From: "Michael S. Tsirkin" <mst@redhat.com>
To: virtio-comment@lists.oasis-open.org, virtio-dev@lists.oasis-open.org
Cc: virtio@lists.oasis-open.org
Subject: [virtio-dev] [PATCH] packed-ring: fix some typos
Date: Thu, 24 Mar 2022 06:34:13 -0400 [thread overview]
Message-ID: <20220324103412.2740-1-mst@redhat.com> (raw)
flag is misnamed in a couple of places.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
packed-ring.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/packed-ring.tex b/packed-ring.tex
index e41f8bf..2accc23 100644
--- a/packed-ring.tex
+++ b/packed-ring.tex
@@ -518,7 +518,7 @@ \subsection{Event Suppression Structure Format}\label{sec:Basic
list.
\drivernormative{\subsection}{Indirect Descriptors}{Basic Facilities of a Virtio Device / Packed Virtqueues / The Virtqueue Descriptor Table / Indirect Descriptors}
-The driver MUST NOT set the DESC_F_INDIRECT flag unless the
+The driver MUST NOT set the VIRTQ_DESC_F_INDIRECT flag unless the
VIRTIO_F_INDIRECT_DESC feature was negotiated. The driver MUST NOT
set any flags except DESC_F_WRITE within an indirect descriptor.
@@ -526,7 +526,7 @@ \subsection{Event Suppression Structure Format}\label{sec:Basic
by the device.
A driver MUST NOT write direct descriptors with
-DESC_F_INDIRECT set in a scatter-gather list linked by
+VIRTQ_DESC_F_INDIRECT set in a scatter-gather list linked by
VIRTQ_DESC_F_NEXT.
\field{flags}.
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next reply other threads:[~2022-03-24 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 10:34 Michael S. Tsirkin [this message]
2022-03-24 11:23 ` [virtio-dev] [PATCH] packed-ring: fix some typos Cornelia Huck
2022-03-24 12:02 ` Michael S. Tsirkin
2022-03-24 12:24 ` [virtio] " Cornelia Huck
2022-04-20 9:46 ` [virtio-comment] " Cornelia Huck
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=20220324103412.2740-1-mst@redhat.com \
--to=mst@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtio@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