From: Parav Pandit <parav@nvidia.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"pasic@linux.ibm.com" <pasic@linux.ibm.com>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"sgarzare@redhat.com" <sgarzare@redhat.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>
Subject: [virtio-dev] RE: [PATCH v11 0/8] Rename queue index to queue number
Date: Tue, 4 Apr 2023 16:37:01 +0000 [thread overview]
Message-ID: <PH0PR12MB5481D042F58691E84A1E31F7DC939@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230404030244-mutt-send-email-mst@kernel.org>
> From: Michael S. Tsirkin <mst@redhat.com>
> Sent: Tuesday, April 4, 2023 3:04 AM
> > Please review.
> > This series fixes the issue [1].
> >
> > [1] https://github.com/oasis-tcs/virtio-spec/issues/163
>
> Could you knock out a version based on Halil's suggestion of using index
> throughout?
Great. Finally, there is an agreement in choosing a word. :)
Will send shortly after interrupt coalescing patches merged to github.
Don't see it there yet.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
prev parent reply other threads:[~2023-04-04 16:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 22:50 [virtio-dev] [PATCH v11 0/8] Rename queue index to queue number Parav Pandit
2023-04-03 22:50 ` [virtio-dev] [PATCH v11 1/8] content: Add vq number text Parav Pandit
2023-04-03 22:50 ` [virtio-dev] [PATCH v11 2/8] transport-pci: Refer to the vq by its number Parav Pandit
2023-04-03 22:50 ` [virtio-dev] [PATCH v11 3/8] transport-mmio: Rename QueueNum register Parav Pandit
2023-04-03 22:50 ` [virtio-dev] [PATCH v11 4/8] transport-mmio: Refer to the vq by its number Parav Pandit
2023-04-03 22:50 ` [virtio-dev] [PATCH v11 5/8] transport-ccw: Rename queue depth/size to other transports Parav Pandit
2023-04-03 22:50 ` [virtio-dev] [PATCH v11 6/8] transport-ccw: Refer to the vq by its number Parav Pandit
2023-04-03 22:50 ` [virtio-dev] [PATCH v11 7/8] virtio-net: Avoid duplicate receive queue example Parav Pandit
2023-04-03 22:50 ` [virtio-dev] [PATCH v11 8/8] virtio-net: Describe RSS using rss rq id Parav Pandit
2023-04-04 7:03 ` [virtio-dev] Re: [PATCH v11 0/8] Rename queue index to queue number Michael S. Tsirkin
2023-04-04 16:37 ` Parav Pandit [this message]
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=PH0PR12MB5481D042F58691E84A1E31F7DC939@PH0PR12MB5481.namprd12.prod.outlook.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=sgarzare@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).