From: Peter Hilber <peter.hilber@opensynergy.com>
To: virtio-comment@lists.oasis-open.org
Cc: Peter Hilber <peter.hilber@opensynergy.com>
Subject: [virtio-comment] [PATCH 2/2] admin: Fix driver requirement subject
Date: Thu, 8 Feb 2024 12:55:45 +0100 [thread overview]
Message-ID: <20240208115545.30102-3-peter.hilber@opensynergy.com> (raw)
In-Reply-To: <20240208115545.30102-1-peter.hilber@opensynergy.com>
The driver-normative section for Group administration commands contains
a requirement on the *device*. This requirement only makes sense as a
requirement on the driver.
Fix this by making the driver the requirement subject.
Fixes: bf1d6b0d24ae8 ("admin: conformance clauses")
Signed-off-by: Peter Hilber <peter.hilber@opensynergy.com>
---
admin.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/admin.tex b/admin.tex
index 54f18c255fb0..41cc12e4e12b 100644
--- a/admin.tex
+++ b/admin.tex
@@ -582,7 +582,7 @@ \section{Administration Virtqueues}\label{sec:Basic Facilities of a Virtio Devic
of \field{struct virtio_admin_cmd} that are a multiple of 64 bit
in length.
-The device MUST supply both device-readable or device-writeable parts
+The driver MUST supply both device-readable or device-writeable parts
of \field{struct virtio_admin_cmd} that are larger than zero in
length. However, \field{command_specific_data} and
\field{command_specific_result} MAY be zero in length, unless
--
2.40.1
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
prev parent reply other threads:[~2024-02-08 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 11:55 [virtio-comment] [PATCH 0/2] admin: Fix requirements wording inconsistencies Peter Hilber
2024-02-08 11:55 ` [virtio-comment] [PATCH 1/2] admin: Refer to processing order as "limited" rather than none Peter Hilber
2024-02-08 11:55 ` Peter Hilber [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240208115545.30102-3-peter.hilber@opensynergy.com \
--to=peter.hilber@opensynergy.com \
--cc=virtio-comment@lists.oasis-open.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).