From: Parav Pandit <parav@nvidia.com>
To: <virtio-comment@lists.linux.dev>, <mst@redhat.com>,
<cohuck@redhat.com>, <mvaralar@redhat.com>
Cc: <shahafs@nvidia.com>, Parav Pandit <parav@nvidia.com>
Subject: [PATCH v1 1/3] device-parts: editorial: Replace duplicated part type
Date: Sun, 20 Oct 2024 14:41:39 +0300 [thread overview]
Message-ID: <20241020114141.451478-2-parav@nvidia.com> (raw)
In-Reply-To: <20241020114141.451478-1-parav@nvidia.com>
Device part type VIRTIO_DEV_PART_VQ_CFG was duplicated in
the description; it is supposed to be VIRTIO_DEV_PART_VQ_NOTIFY_CFG.
Fix it.
Fixes: https://github.com/oasis-tcs/virtio-spec/issues/209
Fixes: 617aa2d62a88 ("Signed-off-by: Parav Pandit <parav@nvidia.com>")
Reviewed-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
device-parts.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/device-parts.tex b/device-parts.tex
index 7197929..e59c0f9 100644
--- a/device-parts.tex
+++ b/device-parts.tex
@@ -75,7 +75,7 @@ \section{Device parts}\label{sec:Basic Facilities of a Virtio Device / Device pa
\field{selector.vq_index.index} is the index of the virtqueue. It is valid
only when the \field{part_type} is VIRTIO_DEV_PART_VQ_CFG or
-VIRTIO_DEV_PART_VQ_CFG.
+VIRTIO_DEV_PART_VQ_NOTIFY_CFG.
\subsection{Common device parts}\label{sec:Basic Facilities of a Virtio Device / Device parts / Common device parts}
--
2.34.1
next prev parent reply other threads:[~2024-10-20 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-20 11:41 [PATCH v1 0/3] virtio-net: Define cvq configuration related device parts Parav Pandit
2024-10-20 11:41 ` Parav Pandit [this message]
2024-10-20 11:41 ` [PATCH v1 2/3] device-parts: Add device type specific raw selector Parav Pandit
2024-10-21 18:12 ` Matias Ezequiel Vara Larsen
2024-10-20 11:41 ` [PATCH v1 3/3] virtio-net: Define cvq configuration related device parts Parav Pandit
2024-11-03 5:15 ` [PATCH v1 0/3] " Parav Pandit
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=20241020114141.451478-2-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=mvaralar@redhat.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.