public inbox for virtio-dev@lists.linux.dev
 help / color / mirror / Atom feed
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 0/2] admin virtqueue fixes
Date: Tue, 2 May 2023 01:44:28 +0300	[thread overview]
Message-ID: <20230501224430.485139-1-parav@nvidia.com> (raw)


Hi Michael,

Please review these two small fixes for the admin virtqueue patches.
They are on top of your work of v12 at [1].

Patch summary:
patch-1 removes PCI transport dependency on deprecated migration bit
patch-2 fixes admin command command data type to be u8 similar to result

[1] https://lore.kernel.org/virtio-comment/cover.1682354275.git.mst@redhat.com/T/#t

Parav Pandit (2):
  admin: Remove dependency on the deprecated register
  admin: Make optional command data type to u8

 admin.tex | 15 ++++++---------
 1 file changed, 6 insertions(+), 9 deletions(-)

-- 
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


             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 Parav Pandit [this message]
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 ` [virtio-dev] [PATCH 2/2] admin: Make optional command data type to u8 Parav Pandit
2023-05-02  7:37   ` [virtio-dev] " 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-1-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