From: Cornelia Huck <cohuck@redhat.com>
To: Parav Pandit <parav@nvidia.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: "virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>,
David Edmondson <david.edmondson@oracle.com>
Subject: [virtio-comment] RE: [virtio-dev] Re: [virtio-comment] RE: [PATCH v6] virtio-net: Improve introductory description
Date: Mon, 20 Feb 2023 14:34:23 +0100 [thread overview]
Message-ID: <87ilfwlau8.fsf@redhat.com> (raw)
In-Reply-To: <PH0PR12MB5481D8AC4A1FA5A9342BB198DCA19@PH0PR12MB5481.namprd12.prod.outlook.com>
On Fri, Feb 17 2023, Parav Pandit <parav@nvidia.com> wrote:
> Yes, can you please withdraw the ballot [1] as it contains stale reference to the patch?
>
> [1] https://www.oasis-open.org/apps/org/workgroup/virtio/ballot.php?id=3758
>
> Also please create new ballot as the github link is now updated for the issue [2].
> [2] https://github.com/oasis-tcs/virtio-spec/issues/156
Done.
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/
prev parent reply other threads:[~2023-02-20 13:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 18:04 [PATCH v6] virtio-net: Improve introductory description Parav Pandit
2023-02-16 14:09 ` [virtio-comment] " Cornelia Huck
2023-02-16 14:30 ` Parav Pandit
2023-02-16 15:49 ` Michael S. Tsirkin
2023-02-16 16:00 ` [virtio-comment] " Parav Pandit
2023-02-16 16:02 ` Parav Pandit
2023-02-16 16:03 ` [virtio-comment] " Cornelia Huck
2023-02-16 16:05 ` [virtio-comment] " Parav Pandit
2023-02-16 16:30 ` [virtio-dev] " Cornelia Huck
2023-02-17 2:59 ` Parav Pandit
2023-02-20 13:34 ` Cornelia Huck [this message]
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=87ilfwlau8.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=david.edmondson@oracle.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=shahafs@nvidia.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