From: Parav Pandit <parav@nvidia.com>
To: <virtio-comment@lists.oasis-open.org>, <mst@redhat.com>,
<cohuck@redhat.com>, <david.edmondson@oracle.com>
Cc: <virtio-dev@lists.oasis-open.org>, <sburla@marvell.com>,
<jasowang@redhat.com>, <yishaih@nvidia.com>, <maorg@nvidia.com>,
<shahafs@nvidia.com>, Parav Pandit <parav@nvidia.com>
Subject: [virtio-comment] [PATCH v9 1/4] admin: Split opcode table rows with a line
Date: Wed, 5 Jul 2023 02:37:21 +0300 [thread overview]
Message-ID: <20230704233724.22394-2-parav@nvidia.com> (raw)
In-Reply-To: <20230704233724.22394-1-parav@nvidia.com>
Currently all opcode appears to be in a single row.
Separate them with a line similar to other tables.
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
changelog:
v2->v3:
- new patch
---
admin.tex | 2 ++
1 file changed, 2 insertions(+)
diff --git a/admin.tex b/admin.tex
index 2efd4d7..e51f9e6 100644
--- a/admin.tex
+++ b/admin.tex
@@ -114,7 +114,9 @@ \subsection{Group administration commands}\label{sec:Basic Facilities of a Virti
opcode & Name & Command Description \\
\hline \hline
0x0000 & VIRTIO_ADMIN_CMD_LIST_QUERY & Provides to driver list of commands supported for this group type \\
+\hline
0x0001 & VIRTIO_ADMIN_CMD_LIST_USE & Provides to device list of commands used for this group type \\
+\hline
0x0002 - 0x7FFF & - & Commands using \field{struct virtio_admin_cmd} \\
\hline
0x8000 - 0xFFFF & - & Reserved for future commands (possibly using a different structure) \\
--
2.26.2
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/
next prev parent reply other threads:[~2023-07-04 23:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 23:37 [virtio-comment] [PATCH v9 0/4] admin: Access legacy registers using admin commands Parav Pandit
2023-07-04 23:37 ` Parav Pandit [this message]
2023-07-05 10:05 ` [virtio-comment] Re: [PATCH v9 1/4] admin: Split opcode table rows with a line Cornelia Huck
2023-07-04 23:37 ` [virtio-comment] [PATCH v9 2/4] admin: Fix section numbering Parav Pandit
2023-07-05 10:09 ` [virtio-comment] " Cornelia Huck
2023-07-05 16:29 ` [virtio-comment] RE: [virtio-dev] " Parav Pandit
2023-07-04 23:37 ` [virtio-comment] [PATCH v9 3/4] admin: Add group member legacy register access commands Parav Pandit
2023-07-05 10:24 ` [virtio-comment] " Cornelia Huck
2023-07-05 16:34 ` [virtio-comment] " Parav Pandit
2023-07-06 5:43 ` [virtio-comment] " Michael S. Tsirkin
2023-07-05 11:04 ` [virtio-comment] " Michael S. Tsirkin
2023-07-05 18:26 ` Parav Pandit
2023-07-06 6:01 ` Michael S. Tsirkin
2023-07-05 22:01 ` Parav Pandit
2023-07-04 23:37 ` [virtio-comment] [PATCH v9 4/4] transport-pci: Introduce group legacy group member config region access Parav Pandit
2023-07-05 10:29 ` [virtio-comment] " Cornelia Huck
2023-07-05 16:36 ` [virtio-comment] " Parav Pandit
2023-07-05 10:56 ` [virtio-comment] " Michael S. Tsirkin
2023-07-05 11:09 ` [virtio-comment] [PATCH v9 0/4] admin: Access legacy registers using admin commands Michael S. Tsirkin
2023-07-05 13:01 ` Parav Pandit
2023-07-05 13:42 ` Cornelia Huck
2023-07-05 14:37 ` Parav Pandit
2023-07-06 4:20 ` Parav Pandit
2023-07-06 6:10 ` 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=20230704233724.22394-2-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=david.edmondson@oracle.com \
--cc=jasowang@redhat.com \
--cc=maorg@nvidia.com \
--cc=mst@redhat.com \
--cc=sburla@marvell.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=yishaih@nvidia.com \
/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).