From: Parav Pandit <parav@nvidia.com>
To: <mst@redhat.com>, <virtio-dev@lists.oasis-open.org>, <cohuck@redhat.com>
Cc: <virtio-comment@lists.oasis-open.org>, <shahafs@nvidia.com>,
Parav Pandit <parav@nvidia.com>
Subject: [virtio-dev] [PATCH 2/2] admin: Make optional command data type to u8
Date: Tue, 2 May 2023 01:44:30 +0300 [thread overview]
Message-ID: <20230501224430.485139-3-parav@nvidia.com> (raw)
In-Reply-To: <20230501224430.485139-1-parav@nvidia.com>
Command data content is specific to command opcode.
This is similar to command result field
command_specific_result.
Hence, make it u8.
This patch is on top of [1].
[1] https://lore.kernel.org/virtio-comment/cover.1682354275.git.mst@redhat.com/T/#t
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
admin.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/admin.tex b/admin.tex
index 037e2e6..648253c 100644
--- a/admin.tex
+++ b/admin.tex
@@ -85,7 +85,7 @@ \subsection{Group administration commands}\label{sec:Basic Facilities of a Virti
/* unused, reserved for future extensions */
u8 reserved1[12];
le64 group_member_id;
- le64 command_specific_data[];
+ u8 command_specific_data[];
/* Device-writable part */
le16 status;
--
2.26.2
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-05-01 22:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 22:44 [virtio-dev] [PATCH 0/2] admin virtqueue fixes Parav Pandit
2023-05-01 22:44 ` [virtio-dev] [PATCH 1/2] admin: Remove dependency on the deprecated register Parav Pandit
2023-05-02 7:39 ` [virtio-dev] " Michael S. Tsirkin
2023-05-01 22:44 ` Parav Pandit [this message]
2023-05-02 7:37 ` [virtio-dev] Re: [PATCH 2/2] admin: Make optional command data type to u8 Michael S. Tsirkin
2023-05-02 11:29 ` [virtio-dev] " Parav Pandit
2023-05-02 11:36 ` [virtio-dev] " Michael S. Tsirkin
2023-05-02 7:41 ` [virtio-dev] Re: [PATCH 0/2] admin virtqueue fixes Michael S. Tsirkin
2023-05-02 11:34 ` [virtio-dev] " Parav Pandit
2023-05-02 11:40 ` [virtio-dev] " Michael S. Tsirkin
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=20230501224430.485139-3-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@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