From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"si-wei.liu@oracle.com" <si-wei.liu@oracle.com>
Subject: Re: [virtio-comment] [PATCH v10] virtio-net: Clarify VLAN filter table configuration
Date: Thu, 26 Jan 2023 11:27:28 -0500 [thread overview]
Message-ID: <20230126112641-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB5481D1CCC1AFB671C20444C1DCCF9@PH0PR12MB5481.namprd12.prod.outlook.com>
On Thu, Jan 26, 2023 at 04:17:30PM +0000, Parav Pandit wrote:
> Because the scope of it beyond just this issue.
You keep using that word. I don't think it means what you think it
means.
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2023-01-26 16:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 21:25 [virtio-comment] [PATCH v10] virtio-net: Clarify VLAN filter table configuration Parav Pandit
2023-01-19 18:35 ` [virtio-comment] " Parav Pandit
2023-01-25 18:04 ` [virtio-comment] " Halil Pasic
2023-01-25 19:09 ` [virtio-dev] " Parav Pandit
2023-01-25 20:31 ` [virtio-dev] " Michael S. Tsirkin
2023-01-25 20:36 ` [virtio-dev] " Parav Pandit
2023-01-26 11:48 ` Halil Pasic
2023-01-26 16:17 ` [virtio-dev] " Parav Pandit
2023-01-26 16:27 ` Michael S. Tsirkin [this message]
2023-01-25 20:55 ` Michael S. Tsirkin
2023-01-25 23:30 ` Parav Pandit
2023-01-25 23:46 ` Parav Pandit
2023-01-26 0:46 ` [virtio-dev] " Si-Wei Liu
2023-01-26 5:01 ` Michael S. Tsirkin
2023-01-26 5:07 ` Michael S. Tsirkin
2023-01-26 16:27 ` Parav Pandit
2023-01-26 16:31 ` Michael S. Tsirkin
2023-01-26 16:42 ` Parav Pandit
2023-01-26 17:15 ` Michael S. Tsirkin
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=20230126112641-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=pasic@linux.ibm.com \
--cc=si-wei.liu@oracle.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