From: Parav Pandit <parav@nvidia.com>
To: <virtio-comment@lists.linux.dev>, <mst@redhat.com>, <cohuck@redhat.com>
Cc: <shahafs@nvidia.com>, Parav Pandit <parav@nvidia.com>,
"Matias Ezequiel Vara Larsen" <mvaralar@redhat.com>
Subject: [PATCH v1 2/5] device-parts: editorial: Fix metadata type name
Date: Mon, 16 Sep 2024 06:08:32 +0300 [thread overview]
Message-ID: <20240916030835.68178-3-parav@nvidia.com> (raw)
In-Reply-To: <20240916030835.68178-1-parav@nvidia.com>
The description is for the type VIRTIO_ADMIN_CMD_DEV_PARTS_METADATA_TYPE_LIST;
however, it referred to a non-existent definition. Correct it.
Branch: virtio-1.4
Fixes: aa4f6f069ab3 ("admin: Add admin commands for device parts")
Fixes: https://github.com/oasis-tcs/virtio-spec/issues/205
Reviewed-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
admin-cmds-device-parts.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/admin-cmds-device-parts.tex b/admin-cmds-device-parts.tex
index 27d8251..3a16692 100644
--- a/admin-cmds-device-parts.tex
+++ b/admin-cmds-device-parts.tex
@@ -152,10 +152,10 @@ \subsubsection{Device parts}\label{sec:Basic Facilities of a Virtio Device / Dev
device responds with \field{hdr_list_count.count}. The
\field{hdr_list_count.count} indicates an count of
\field{struct virtio_dev_part_hdr} metadata entries that the device can
-provide when the \field{type} is set to VIRTIO_ADMIN_CMD_DEV_PARTS_METADATA_TYPE_HDR
+provide when the \field{type} is set to VIRTIO_ADMIN_CMD_DEV_PARTS_METADATA_TYPE_LIST
in a subsequent VIRTIO_ADMIN_CMD_DEV_PARTS_METADATA_GET command.
-When \field{type} is set to VIRTIO_ADMIN_CMD_DEV_PARTS_METADATA_TYPE_HDR,
+When \field{type} is set to VIRTIO_ADMIN_CMD_DEV_PARTS_METADATA_TYPE_LIST,
the device responds with \field{hdr_list}. \field{hdr_list}
indicates the device parts metadata.
--
2.34.1
next prev parent reply other threads:[~2024-09-16 3:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 3:08 [PATCH v1 0/5] Assorted editorial fixes Parav Pandit
2024-09-16 3:08 ` [PATCH v1 1/5] device-parts: editorial: Add missing struct keyword Parav Pandit
2024-09-16 3:08 ` Parav Pandit [this message]
2024-09-16 3:08 ` [PATCH v1 3/5] crypto: editorial: Fix spelling errors Parav Pandit
2024-09-16 3:08 ` [PATCH v1 4/5] gpu: " Parav Pandit
2024-09-16 3:08 ` [PATCH v1 5/5] common: " Parav Pandit
2024-09-16 3:11 ` [PATCH v1 0/5] Assorted editorial fixes Parav Pandit
2024-09-16 8:35 ` Michael S. Tsirkin
2024-09-16 9:13 ` Parav Pandit
2024-09-25 11:33 ` 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=20240916030835.68178-3-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.