From: Jiri Pirko <jiri@nvidia.com>
To: Parav Pandit <parav@nvidia.com>
Cc: mst@redhat.com, virtio-dev@lists.oasis-open.org,
cohuck@redhat.com, virtio-comment@lists.oasis-open.org,
shahafs@nvidia.com
Subject: Re: [virtio-dev] [PATCH 3/3] transport-mmio: Refer to the vq by its number
Date: Fri, 24 Feb 2023 11:06:35 +0100 [thread overview]
Message-ID: <Y/iMK0z07mNc76Jd@nanopsycho> (raw)
In-Reply-To: <20230223054624.168042-4-parav@nvidia.com>
Thu, Feb 23, 2023 at 06:46:24AM CET, parav@nvidia.com wrote:
>Currently specification uses virtqueue index and
>number interchangeably to refer to the virtqueue.
>
>Instead refer to it by its number.
>
>This patch is on top of [1].
>
>[1] https://lists.oasis-open.org/archives/virtio-dev/202302/msg00527.html
>
>Fixes: https://github.com/oasis-tcs/virtio-spec/issues/163
>Signed-off-by: Parav Pandit <parav@nvidia.com>
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
next prev parent reply other threads:[~2023-02-24 10:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 5:46 [PATCH 0/3] Rename queue index to queue number Parav Pandit
2023-02-23 5:46 ` [PATCH 1/3] transport-pci: Refer to the vq by its number Parav Pandit
2023-02-24 10:05 ` [virtio-dev] " Jiri Pirko
2023-02-23 5:46 ` [PATCH 2/3] transport-mmio: Rename QueueNum register Parav Pandit
2023-02-24 10:06 ` [virtio-dev] " Jiri Pirko
2023-02-27 17:36 ` Michael S. Tsirkin
2023-02-23 5:46 ` [PATCH 3/3] transport-mmio: Refer to the vq by its number Parav Pandit
2023-02-24 10:06 ` Jiri Pirko [this message]
2023-02-27 8:45 ` [virtio-comment] Re: [PATCH 0/3] Rename queue index to queue number Cornelia Huck
2023-02-27 16:00 ` Parav Pandit
2023-02-27 17:33 ` [virtio-dev] " Michael S. Tsirkin
[not found] ` <20230301182207.23f995cd.pasic@linux.ibm.com>
[not found] ` <20230301123044-mutt-send-email-mst@kernel.org>
[not found] ` <87a60vmbub.fsf@redhat.com>
[not found] ` <20230303023949-mutt-send-email-mst@kernel.org>
2023-03-03 21:49 ` [virtio-comment] Re: [virtio-dev] Re: [virtio-comment] " Halil Pasic
2023-03-05 9:51 ` Michael S. Tsirkin
2023-03-09 16:46 ` Halil Pasic
2023-03-09 16:53 ` Michael S. Tsirkin
2023-03-10 14:05 ` Halil Pasic
2023-02-27 17:39 ` Michael S. Tsirkin
[not found] ` <20230302165216.1293d066.pasic@linux.ibm.com>
[not found] ` <PH0PR12MB54810632DAE7C0D8BEABC9E9DCB29@PH0PR12MB5481.namprd12.prod.outlook.com>
2023-03-03 15:38 ` [virtio-comment] " Halil Pasic
2023-03-05 9:29 ` Michael S. Tsirkin
[not found] ` <20230302183736-mutt-send-email-mst@kernel.org>
2023-03-07 15:20 ` 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=Y/iMK0z07mNc76Jd@nanopsycho \
--to=jiri@nvidia.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.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