From: Parav Pandit <parav@nvidia.com>
To: hengqi@linux.alibaba.com, sburla@marvell.com,
si-wei.liu@oracle.com, virtio-comment@lists.oasis-open.org,
virtio@lists.oasis-open.org, xuanzhuo@linux.alibaba.com,
Parav Pandit <parav@nvidia.com>
Subject: [virtio-comment] virtio-net collaboration bi-weekly
Date: Wed, 10 Jan 2024 03:45:55 +0000 [thread overview]
Message-ID: <calendar-f31007d9-6ee0-47ad-b2c2-86e16fbe73c4@google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]
Gentle remind and test message for new meeting invite this year.
virtio-net collaboration bi-weekly
Wednesday Jan 10, 2024 ⋅ 10:30am – 11:15am
India Standard Time - Kolkata
Join with Google Meet
https://meet.google.com/gkj-rawi-ufp?hs=224
Join by phone
(US) +1 978-403-0584
PIN: 756969764
More phone numbers
https://tel.meet/gkj-rawi-ufp?pin=7573680783326&hs=0
Attachments
virtio-net collaboration bi-weekly meeting notes
https://docs.google.com/document/u/1/d/1ME-jFncvPMwH_GyeLhhIYgqmFhTAblsIopqHCZZxufM/edit
Hi All,This is a bi-weekly collaboration meeting for virtio net
specification developers.Renewing the series. Meeting agenda and minutes
are captured at [1].[1]
https://docs.google.com/document/d/1ME-jFncvPMwH_GyeLhhIYgqmFhTAblsIopqHCZZxufM/edit?usp=sharing -------a.
All decisions are still made by TC electronic ballot as usual. Proposed
collaboration meetings are unrelated to TC ballot.b. All discussions follow
OASIS feedback license.
https://www.oasis-open.org/policies-guidelines/ipr/#appendixa
Organizer
Parav Pandit
parav@nvidia.com
Guests
Parav Pandit - organizer
hengqi@linux.alibaba.com
sburla@marvell.com
si-wei.liu@oracle.com
virtio-comment@lists.oasis-open.org
virtio@lists.oasis-open.org
xuanzhuo@linux.alibaba.com
[-- Attachment #2: Type: text/html, Size: 25927 bytes --]
next reply other threads:[~2024-01-10 3:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 3:45 Parav Pandit [this message]
2024-01-10 3:55 ` [virtio-comment] Re: virtio-net collaboration bi-weekly Xuan Zhuo
2024-01-10 4:42 ` [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=calendar-f31007d9-6ee0-47ad-b2c2-86e16fbe73c4@google.com \
--to=parav@nvidia.com \
--cc=hengqi@linux.alibaba.com \
--cc=sburla@marvell.com \
--cc=si-wei.liu@oracle.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio@lists.oasis-open.org \
--cc=xuanzhuo@linux.alibaba.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).