From: Parav Pandit <parav@nvidia.com>
To: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Cc: "hengqi@linux.alibaba.com" <hengqi@linux.alibaba.com>,
"sburla@marvell.com" <sburla@marvell.com>,
"si-wei.liu@oracle.com" <si-wei.liu@oracle.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"virtio@lists.oasis-open.org" <virtio@lists.oasis-open.org>
Subject: [virtio-comment] RE: virtio-net collaboration bi-weekly
Date: Wed, 10 Jan 2024 04:42:34 +0000 [thread overview]
Message-ID: <PH0PR12MB5481E125C27A45B5E38C534CDC692@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1704858929.6283097-1-xuanzhuo@linux.alibaba.com>
> From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> Sent: Wednesday, January 10, 2024 9:25 AM
> To: Parav Pandit <parav@nvidia.com>
> Cc: hengqi@linux.alibaba.com; sburla@marvell.com; si-wei.liu@oracle.com;
> virtio-comment@lists.oasis-open.org; virtio@lists.oasis-open.org; Parav
> Pandit <parav@nvidia.com>
> Subject: Re: virtio-net collaboration bi-weekly
>
> Sorry, I and Heng Qi are busy today, so we can not attend this meeting.
>
Thanks for the update, Xuan.
Will capture the meetings and slides at public shared regular place for your later reference.
> Thanks.
>
>
>
> On Wed, 10 Jan 2024 03:45:55 +0000, Parav Pandit <parav@nvidia.com>
> wrote:
> > 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_GyeLhhIYgqmFhTAbl
> > sIopqHCZZxufM/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
> >
> >
> >
next prev parent reply other threads:[~2024-01-10 4:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 3:45 [virtio-comment] virtio-net collaboration bi-weekly Parav Pandit
2024-01-10 3:55 ` [virtio-comment] " Xuan Zhuo
2024-01-10 4:42 ` Parav Pandit [this message]
[not found] <PH0PR12MB5481DBEAA12D6B22289D99E6DC4EA@PH0PR12MB5481.namprd12.prod.outlook.com>
2023-06-07 6:08 ` [virtio-comment] " Parav Pandit
2023-06-26 3:04 ` Parav Pandit
2023-07-16 20:00 ` Parav Pandit
2023-11-08 6:36 ` Parav Pandit
2023-11-22 10:19 ` 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=PH0PR12MB5481E125C27A45B5E38C534CDC692@PH0PR12MB5481.namprd12.prod.outlook.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).