From: "Zhu, Lingshan" <lingshan.zhu@intel.com>
To: Parav Pandit <parav@nvidia.com>,
Zhu Lingshan <lingshan.zhu@linux.intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"sgarzare@redhat.com" <sgarzare@redhat.com>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"nrupal.jani@intel.com" <nrupal.jani@intel.com>,
"Piotr.Uminski@intel.com" <Piotr.Uminski@intel.com>,
"hang.yuan@intel.com" <hang.yuan@intel.com>
Cc: "virtio@lists.oasis-open.org" <virtio@lists.oasis-open.org>,
Jiri Pirko <jiri@nvidia.com>,
"pasic@linux.ibm.com" <pasic@linux.ibm.com>,
Shahaf Shuler <shahafs@nvidia.com>,
Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: Re: [virtio-dev] [PATCH v11 08/10] admin: command list discovery
Date: Fri, 7 Apr 2023 10:01:37 +0800 [thread overview]
Message-ID: <fc449c23-9fd0-e6a4-b147-458b874ed3c8@intel.com> (raw)
In-Reply-To: <PH0PR12MB548174BC1333E7107B731108DC919@PH0PR12MB5481.namprd12.prod.outlook.com>
On 4/6/2023 10:05 PM, Parav Pandit wrote:
>
>> From: Zhu Lingshan <lingshan.zhu@linux.intel.com>
>> Sent: Thursday, April 6, 2023 3:20 AM
> I have a dumb question.
> Zhu responded to these patches.
> Some patches have prefix appended as "virtio", some has "virtio-dev", and some have "virtio-comment".
> Whichever tool is adding it prefix, why it cannot keep the simple consistency?
>
> Do we need to ask OASIS about it?
one of the reasons is that I subscribed virtio, virtio-comment and
virtio-dev, and these threads list are all in the to or cc recipients.
I agree OASIS mailing server sometimes behave oddly, it is reliable most
of the time, but I didn't receive any direct emails from you about
the virtio-net Sub-TC proposal, but I can receive emails from Stefan.
That's odd, I should see all your emails via virtio@list.oasis-open.org.
>
>
---------------------------------------------------------------------
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-04-07 2:02 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 15:02 [virtio-dev] [PATCH v11 00/10] Introduce device group and device management Michael S. Tsirkin
2023-04-03 15:03 ` [virtio-dev] [PATCH v11 01/10] virtio: document forward compatibility guarantees Michael S. Tsirkin
2023-04-06 7:15 ` [virtio-dev] " Zhu, Lingshan
2023-04-03 15:03 ` [virtio-dev] [PATCH v11 02/10] admin: introduce device group and related concepts Michael S. Tsirkin
2023-04-04 11:38 ` [virtio-dev] " Stefan Hajnoczi
2023-04-06 3:42 ` Parav Pandit
2023-04-10 13:23 ` Michael S. Tsirkin
2023-04-10 16:42 ` [virtio-dev] " Parav Pandit
2023-04-24 16:30 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-04-24 16:45 ` [virtio-dev] RE: [virtio] " Parav Pandit
2023-04-24 20:32 ` [virtio-dev] " Michael S. Tsirkin
2023-04-06 7:16 ` [virtio-dev] " Zhu, Lingshan
2023-04-03 15:03 ` [virtio-dev] [PATCH v11 03/10] admin: introduce group administration commands Michael S. Tsirkin
2023-04-04 11:50 ` [virtio-dev] " Stefan Hajnoczi
2023-04-06 3:58 ` Parav Pandit
2023-04-06 7:16 ` Zhu, Lingshan
2023-04-03 15:03 ` [virtio-dev] [PATCH v11 04/10] admin: introduce virtio admin virtqueues Michael S. Tsirkin
2023-04-04 11:58 ` [virtio-dev] " Stefan Hajnoczi
2023-04-06 4:08 ` Parav Pandit
2023-04-10 13:22 ` Michael S. Tsirkin
2023-04-10 14:22 ` [virtio-dev] " Parav Pandit
2023-04-10 20:04 ` [virtio-dev] " Michael S. Tsirkin
2023-04-11 13:39 ` [virtio-dev] " Parav Pandit
2023-04-11 14:01 ` [virtio-dev] " Michael S. Tsirkin
2023-04-11 15:46 ` [virtio-dev] " Parav Pandit
2023-04-06 7:17 ` [virtio-dev] " Zhu Lingshan
2023-04-03 15:03 ` [virtio-dev] [PATCH v11 05/10] pci: add admin vq registers to virtio over pci Michael S. Tsirkin
2023-04-04 12:52 ` [virtio-dev] " Stefan Hajnoczi
2023-04-06 4:14 ` Parav Pandit
2023-04-24 15:36 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-04-06 7:17 ` [virtio-dev] Re: [virtio] " Zhu, Lingshan
2023-04-03 15:03 ` [virtio-dev] [PATCH v11 06/10] mmio: document ADMIN_VQ as reserved Michael S. Tsirkin
2023-04-03 15:54 ` [virtio-dev] " Parav Pandit
2023-04-24 15:38 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-04-06 7:18 ` [virtio-dev] Re: [virtio-comment] " Zhu Lingshan
2023-04-03 15:03 ` [virtio-dev] [PATCH v11 07/10] ccw: " Michael S. Tsirkin
2023-04-03 15:55 ` [virtio-dev] " Parav Pandit
2023-04-03 17:29 ` Michael S. Tsirkin
2023-04-06 4:15 ` Parav Pandit
2023-04-06 7:18 ` [virtio-dev] " Zhu Lingshan
2023-04-03 15:03 ` [virtio-dev] [PATCH v11 08/10] admin: command list discovery Michael S. Tsirkin
2023-04-04 12:57 ` [virtio-dev] " Stefan Hajnoczi
2023-04-06 4:27 ` Parav Pandit
2023-04-24 16:13 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-04-06 7:20 ` [virtio-dev] " Zhu Lingshan
2023-04-06 14:05 ` Parav Pandit
2023-04-07 2:01 ` Zhu, Lingshan [this message]
2023-04-07 7:34 ` Michael S. Tsirkin
2023-04-03 15:03 ` [virtio-dev] [PATCH v11 09/10] admin: conformance clauses Michael S. Tsirkin
2023-04-04 13:03 ` [virtio-dev] " Stefan Hajnoczi
2023-04-06 7:30 ` [virtio-dev] Re: [virtio] " Zhu, Lingshan
2023-04-24 16:17 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-04-03 15:04 ` [virtio-dev] [PATCH v11 10/10] ccw: document more reserved features Michael S. Tsirkin
2023-04-06 7:31 ` [virtio-dev] Re: [virtio-comment] " Zhu Lingshan
2023-04-03 15:59 ` [virtio-dev] Re: [PATCH v11 00/10] Introduce device group and device management Parav Pandit
2023-04-03 16:39 ` Cornelia Huck
2023-04-03 17:31 ` Michael S. Tsirkin
2023-04-04 8:10 ` Cornelia Huck
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=fc449c23-9fd0-e6a4-b147-458b874ed3c8@intel.com \
--to=lingshan.zhu@intel.com \
--cc=Piotr.Uminski@intel.com \
--cc=cohuck@redhat.com \
--cc=hang.yuan@intel.com \
--cc=jasowang@redhat.com \
--cc=jiri@nvidia.com \
--cc=lingshan.zhu@linux.intel.com \
--cc=mgurtovoy@nvidia.com \
--cc=mst@redhat.com \
--cc=nrupal.jani@intel.com \
--cc=parav@nvidia.com \
--cc=pasic@linux.ibm.com \
--cc=sgarzare@redhat.com \
--cc=shahafs@nvidia.com \
--cc=stefanha@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtio@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