All of lore.kernel.org
 help / color / mirror / Atom feed
From: Parav Pandit <parav@nvidia.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "virtio@lists.oasis-open.org" <virtio@lists.oasis-open.org>,
	"virtio-comment@lists.oasis-open.org"
	<virtio-comment@lists.oasis-open.org>
Subject: [virtio-comment] RE: [virtio] Re: [virtio-comment] virtio networking collaboration meeting: call for agenda
Date: Thu, 1 Jun 2023 16:19:36 +0000	[thread overview]
Message-ID: <PH0PR12MB54816AC81BE03DC46848B2C0DC499@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230601121137-mutt-send-email-mst@kernel.org>


> From: virtio@lists.oasis-open.org <virtio@lists.oasis-open.org> On Behalf Of
> Michael S. Tsirkin
> Sent: Thursday, June 1, 2023 12:14 PM
> 
> On Thu, May 18, 2023 at 12:53:56AM +0000, Parav Pandit wrote:
> > For the first meeting, I propose the following agenda item:
> > - discuss new virtio net device features for 1.4 spec release
> 
> Want to include a bit more detail here?  What do you want to discuss? At the
> moment the only thing I see on list is inner hash proposal.

Yes, I would like to discuss list of features to go through at high level.
In process of creating virtio-docs patch that we can review and store.
Will send out the link hopefully in couple of hours.

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/


  reply	other threads:[~2023-06-01 16:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18  0:53 [virtio-comment] virtio networking collaboration meeting: call for agenda Parav Pandit
2023-05-18  5:47 ` Ariel Adam
2023-05-18  9:33   ` Eugenio Perez Martin
2023-05-18 16:53     ` Chet Ensign
2023-05-18 18:46       ` Michael S. Tsirkin
2023-05-18 19:09         ` [virtio-comment] Re: [virtio] " Chet Ensign
2023-05-18 19:31           ` Michael S. Tsirkin
2023-05-18 19:45             ` Chet Ensign
2023-05-21 20:58   ` Parav Pandit
2023-05-22  2:45     ` Xuan Zhuo
2023-05-30 14:57       ` Parav Pandit
2023-05-30 18:41     ` [virtio-comment] Re: [virtio] " Michael S. Tsirkin
2023-05-31 15:16 ` [virtio-comment] " Satananda Burla
2023-05-31 22:22 ` [virtio-comment] " Si-Wei Liu
2023-06-01  0:33   ` Parav Pandit
2023-06-01 15:14     ` Parav Pandit
2023-06-01 16:14 ` Michael S. Tsirkin
2023-06-01 16:19   ` Parav Pandit [this message]
2023-06-01 16:26     ` [virtio-comment] Re: [virtio] " Michael S. Tsirkin
2023-06-01 16:35       ` [virtio-comment] " 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=PH0PR12MB54816AC81BE03DC46848B2C0DC499@PH0PR12MB5481.namprd12.prod.outlook.com \
    --to=parav@nvidia.com \
    --cc=mst@redhat.com \
    --cc=virtio-comment@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.