From: Cornelia Huck <cohuck@redhat.com>
To: Parav Pandit <parav@nvidia.com>,
virtio-comment@lists.oasis-open.org, mst@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-dev] Re: [PATCH v9 1/4] admin: Split opcode table rows with a line
Date: Wed, 05 Jul 2023 12:05:24 +0200 [thread overview]
Message-ID: <87lefu3c7v.fsf@redhat.com> (raw)
In-Reply-To: <20230704233724.22394-2-parav@nvidia.com>
On Wed, Jul 05 2023, Parav Pandit <parav@nvidia.com> wrote:
> 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(+)
>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
---------------------------------------------------------------------
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-07-05 10:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 23:37 [virtio-dev] [PATCH v9 0/4] admin: Access legacy registers using admin commands Parav Pandit
2023-07-04 23:37 ` [virtio-dev] [PATCH v9 1/4] admin: Split opcode table rows with a line Parav Pandit
2023-07-05 10:05 ` Cornelia Huck [this message]
2023-07-04 23:37 ` [virtio-dev] [PATCH v9 2/4] admin: Fix section numbering Parav Pandit
2023-07-05 10:09 ` [virtio-dev] " Cornelia Huck
2023-07-05 16:29 ` Parav Pandit
2023-07-04 23:37 ` [virtio-dev] [PATCH v9 3/4] admin: Add group member legacy register access commands Parav Pandit
2023-07-05 10:24 ` [virtio-dev] " Cornelia Huck
2023-07-05 16:34 ` [virtio-dev] " Parav Pandit
2023-07-06 5:43 ` [virtio-dev] " Michael S. Tsirkin
2023-07-05 11:04 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-07-05 18:26 ` [virtio-dev] " Parav Pandit
2023-07-06 6:01 ` [virtio-dev] " Michael S. Tsirkin
2023-07-05 22:01 ` [virtio-dev] " Parav Pandit
2023-07-04 23:37 ` [virtio-dev] [PATCH v9 4/4] transport-pci: Introduce group legacy group member config region access Parav Pandit
2023-07-05 10:29 ` [virtio-dev] " Cornelia Huck
2023-07-05 16:36 ` [virtio-dev] " Parav Pandit
2023-07-05 10:56 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-07-05 11:09 ` [virtio-dev] Re: [virtio-comment] [PATCH v9 0/4] admin: Access legacy registers using admin commands Michael S. Tsirkin
2023-07-05 13:01 ` [virtio-dev] " 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 ` [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=87lefu3c7v.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=david.edmondson@oracle.com \
--cc=jasowang@redhat.com \
--cc=maorg@nvidia.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.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