[PATCH] virtio-ccw: relax device requirement for revision-specific command rejection

[Cornelia Huck <cohuck@redhat.com>]

The device is currently required to reject any command that is
not contained in the negotiated revision. Some implementations
did not actively check for the revision when processing a command;
retroactively changing these implementations can break existing
drivers.

Relaxing the rejection requirement to SHOULD makes these existing
device implementations compliant, and will not have any effect on
drivers that did not send any commands for wrong revisions.

Fixes: https://github.com/oasis-tcs/virtio-spec/issues/96

Signed-off-by: Cornelia Huck <cohuck@redhat.com>
---
 content.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content.tex b/content.tex
index 835f1ea5ebaa..b72bad0dddaa 100644
--- a/content.tex
+++ b/content.tex
@@ -2396,7 +2396,7 @@ \subsubsection{Setting the Virtio Revision}\label{sec:Virtio Transport Options /
 and \field{data}, it MUST post a unit check with command reject as well. A
 non-transitional device MUST reject revision id 0.
 
-A device MUST answer with command reject to any virtio-ccw specific
+A device SHOULD answer with command reject to any virtio-ccw specific
 channel command that is not contained in the revision selected by the
 driver.
 
-- 
2.26.2