From: "Michael S. Tsirkin" <mst@redhat.com>
To: 何磊 <helei.sig11@bytedance.com>
Cc: virtio-comment@lists.oasis-open.org, pizhenwei@bytedance.com,
xin.zeng@intel.com, arei.gonglei@huawei.com
Subject: Re: [virtio-comment] PING: [V3 PATCH 1/1] virtio-crypto: introduce akcipher service
Date: Fri, 17 Jun 2022 06:21:27 -0400 [thread overview]
Message-ID: <20220617062005-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <B6D469D5-DF74-4B76-AA22-522750BF6B89@bytedance.com>
On Tue, Dec 21, 2021 at 10:40:02AM +0800, 何磊 wrote:
> Ping
So the vote on this failed since the TC wanted to defer until
after 1.2. Now that freeze is behind us I will restart the
ballot.
--
MST
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:[~2022-06-17 10:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 12:53 [virtio-comment] [V3 PATCH 0/1] Introduce virtio asymmetric crypto service Lei He
2021-12-10 12:53 ` [virtio-comment] [V3 PATCH 1/1] virtio-crypto: introduce akcipher service Lei He
2021-12-21 2:40 ` [virtio-comment] PING: " 何磊
2022-06-17 10:21 ` Michael S. Tsirkin [this message]
2022-06-17 11:55 ` [virtio-comment] Re: [External] " 何磊
2022-01-10 12:20 ` 何磊
2022-01-10 12:55 ` [virtio-comment] " Michael S. Tsirkin
2022-01-15 17:37 ` Michael S. Tsirkin
2022-01-16 7:18 ` [virtio-comment] Re: [Phishing Risk] [External] " 何磊
2022-01-11 3:14 ` [virtio-comment] " 何磊
2022-01-19 15:17 ` Michael S. Tsirkin
[not found] ` <3bc3a06782b943e8a43b07954ba328fd@huawei.com>
2022-01-20 7:26 ` Michael S. Tsirkin
[not found] ` <46e69803beeb4741a33c89e2351370ab@huawei.com>
2022-01-20 10:47 ` 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=20220617062005-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=helei.sig11@bytedance.com \
--cc=pizhenwei@bytedance.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=xin.zeng@intel.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