From: Parav Pandit <parav@nvidia.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: "mst@redhat.com" <mst@redhat.com>,
"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>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>, Jiri Pirko <jiri@nvidia.com>
Subject: [virtio-dev] RE: [virtio-comment] [PATCH v6 4/8] transport-mmio: Refer to the vq by its number
Date: Mon, 27 Mar 2023 14:14:24 +0000 [thread overview]
Message-ID: <PH0PR12MB54813AFD0C455B5A3BAE8BB5DC8B9@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <tzpnzzvujby6vep2ja34x5vz2dvi2nyzr4i6ssj4z2t46zqnzj@llrivtyqnnn3>
> From: Stefano Garzarella <sgarzare@redhat.com>
> Sent: Monday, March 27, 2023 9:59 AM
> >>
> >With Michael suggestion, the first patch describes the vq number range.
>
> I see.
>
> >I think we can drop this duplicate text from here all together.
> >
>
> Yep, I agree on that.
Ok. thanks.
Will send v7 fixing this.
---------------------------------------------------------------------
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-03-27 14:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 1:04 [virtio-dev] [PATCH v6 0/8] Rename queue index to queue number Parav Pandit
2023-03-24 1:04 ` [virtio-dev] [PATCH v6 1/8] content: Add vq number text Parav Pandit
2023-03-24 1:04 ` [virtio-dev] [PATCH v6 2/8] transport-pci: Refer to the vq by its number Parav Pandit
2023-03-24 1:04 ` [virtio-dev] [PATCH v6 3/8] transport-mmio: Rename QueueNum register Parav Pandit
2023-03-24 1:04 ` [virtio-dev] [PATCH v6 4/8] transport-mmio: Refer to the vq by its number Parav Pandit
2023-03-27 10:03 ` [virtio-dev] Re: [virtio-comment] " Stefano Garzarella
2023-03-27 13:41 ` [virtio-dev] " Parav Pandit
2023-03-27 13:58 ` [virtio-dev] " Stefano Garzarella
2023-03-27 14:14 ` Parav Pandit [this message]
2023-03-24 1:04 ` [virtio-dev] [PATCH v6 5/8] transport-ccw: Rename queue depth/size to other transports Parav Pandit
2023-03-24 1:04 ` [virtio-dev] [PATCH v6 6/8] transport-ccw: Refer to the vq by its number Parav Pandit
2023-03-24 1:04 ` [virtio-dev] [PATCH v6 7/8] virtio-net: Avoid duplicate receive queue example Parav Pandit
2023-03-24 1:04 ` [virtio-dev] [PATCH v6 8/8] virtio-net: Describe RSS using rss rq id 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=PH0PR12MB54813AFD0C455B5A3BAE8BB5DC8B9@PH0PR12MB5481.namprd12.prod.outlook.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=jiri@nvidia.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 NNTP newsgroup(s).