[PATCH 1/2] ccw: Further use of RFC2119 language.

Some more instances of MAY and SHOULD, as reported in TAB comments
TAB-548 and TAB-550.

Signed-off-by: Cornelia Huck <>
---
 content.tex |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/content.tex b/content.tex
index ed2c3fa..96c4fc8 100644
--- a/content.tex
+++ b/content.tex
@@ -2194,7 +2194,7 @@ for the devices are contained, starting at bit_nr, one bit per
 virtqueue of the device. Bit numbers start at the left, i.e. the most
 significant bit in the first byte is assigned the bit number 0.
 isc contains the I/O interruption subclass to be used for the adapter
-I/O interrupt. It may be different from the isc used by the proxy
+I/O interrupt. It MAY be different from the isc used by the proxy
 virtio-ccw device's subchannel.
 No padding is added at the end of the structure, it is exactly 25 bytes
 in length.
@@ -2283,10 +2283,10 @@ The device MUST ignore bits 0-31 (counting from the left) of GPR2.
 This aligns passing the subchannel ID with the way it is passed
 for the existing I/O instructions.
 
-Host cookie is an optional per-virtqueue 64 bit value that can be
+Host cookie is an optional per-virtqueue 64 bit value that MAY be
 used by the hypervisor to speed up the notification execution.
 For each notification, the output value is returned in GPR2 and
-should be passed in GPR4 for the next notification:
+SHOULD be passed in GPR4 for the next notification:
 
 \begin{lstlisting}
 info->cookie = do_notify(schid,
-- 
1.7.9.5