From: Parav Pandit <parav@nvidia.com>
To: "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>
Cc: "virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>, Jiri Pirko <jiri@nvidia.com>,
Stefano Garzarella <sgarzare@redhat.com>
Subject: [virtio-dev] RE: [PATCH v7 4/8] transport-mmio: Refer to the vq by its number
Date: Mon, 27 Mar 2023 20:56:53 +0000 [thread overview]
Message-ID: <PH0PR12MB548122E4F3C6431CEF907074DC8B9@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230327205359.406605-5-parav@nvidia.com>
+ Stefano
> From: Parav Pandit <parav@nvidia.com>
> Sent: Monday, March 27, 2023 4:54 PM
> To: mst@redhat.com; virtio-dev@lists.oasis-open.org; pasic@linux.ibm.com;
> cohuck@redhat.com
> Cc: virtio-comment@lists.oasis-open.org; Shahaf Shuler <shahafs@nvidia.com>;
> Parav Pandit <parav@nvidia.com>; Jiri Pirko <jiri@nvidia.com>
> Subject: [PATCH v7 4/8] transport-mmio: Refer to the vq by its number
While using my old send script, I missed to include you.
I am sorry about it.
Will take care next time to add you.
Please review.
---------------------------------------------------------------------
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 20:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 20:53 [virtio-dev] [PATCH v7 0/8] Rename queue index to queue number Parav Pandit
2023-03-27 20:53 ` [virtio-dev] [PATCH v7 1/8] content: Add vq number text Parav Pandit
2023-03-27 20:53 ` [virtio-dev] [PATCH v7 2/8] transport-pci: Refer to the vq by its number Parav Pandit
2023-03-27 20:53 ` [virtio-dev] [PATCH v7 3/8] transport-mmio: Rename QueueNum register Parav Pandit
2023-03-27 20:53 ` [virtio-dev] [PATCH v7 4/8] transport-mmio: Refer to the vq by its number Parav Pandit
2023-03-27 20:56 ` Parav Pandit [this message]
2023-03-27 20:53 ` [virtio-dev] [PATCH v7 5/8] transport-ccw: Rename queue depth/size to other transports Parav Pandit
2023-03-27 20:53 ` [virtio-dev] [PATCH v7 6/8] transport-ccw: Refer to the vq by its number Parav Pandit
2023-03-27 20:53 ` [virtio-dev] [PATCH v7 7/8] virtio-net: Avoid duplicate receive queue example Parav Pandit
2023-03-27 20:53 ` [virtio-dev] [PATCH v7 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=PH0PR12MB548122E4F3C6431CEF907074DC8B9@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).