From: Cornelia Huck <cohuck@redhat.com>
To: Lei He <helei.sig11@bytedance.com>,
mst@redhat.com, virtio-comment@lists.oasis-open.org
Cc: helei.sig11@bytedance.com, xin.zeng@intel.com,
arei.gonglei@huawei.com, pizhenwei@bytedance.com
Subject: Re: Re: [virtio-comment] [PATCH v4 1/1] virtio-crypto: introduce akcipher service
Date: Mon, 18 Jul 2022 13:47:50 +0200 [thread overview]
Message-ID: <87r12iprq1.fsf@redhat.com> (raw)
In-Reply-To: <6ae5062f-e839-23a6-d000-5b6fd82158f4@bytedance.com>
On Mon, Jul 18 2022, Lei He <helei.sig11@bytedance.com> wrote:
> On 2022/6/21 下午6:19, Cornelia Huck wrote:
>> On Tue, Jun 21 2022, Lei He <helei.sig11@bytedance.com> wrote:
>>
>>> Introduce akcipher (asymmetric key cipher) service type, several
>>> asymmetric algorithms and relevent information:
>>> - RSA(padding algorithm, ASN.1 schema definition)
>>> - ECDSA(ECC algorithm)
>>>
>>> Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
>>> Signed-off-by: Lei He <helei.sig11@bytedance.com>
>>> ---
>>> introduction.tex | 18 +++
>>> virtio-crypto.tex | 351 +++++++++++++++++++++++++++++++++++++++++++++++++++++-
>>> 2 files changed, 363 insertions(+), 6 deletions(-)
>>
>> Hm, there's currently a ballot running on v3... I assume you want the
>> changes in v4 instead?
>>
>> Do you want to withdraw the ballot (and re-initiate voting for v4)?
>>
>
> Hi, Huck:
> It looks like the linux kernel won't accept the ECDSA related patch at
> the moment, let's re-initiate voting for v4? Do I need to start an new
> issue on github?
Ok, can you quickly summarize the state for me? Are we going with the
version in v3 or in v4? I've lost track here.
Please don't open a new github issue, just edit the existing one to
point to the change you want to see included.
Thanks,
Cornelia
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-07-18 11:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 10:04 [virtio-comment] [PATCH v4 0/1] Introduce virtio asymmetric crypto service Lei He
2022-06-21 10:04 ` [virtio-comment] [PATCH v4 1/1] virtio-crypto: introduce akcipher service Lei He
2022-06-21 10:19 ` Cornelia Huck
2022-06-21 10:24 ` [virtio-comment] Re: [External] " 何磊
2022-06-21 10:34 ` Cornelia Huck
2022-06-21 10:36 ` [virtio-comment] " 何磊
2022-07-18 10:10 ` Lei He
2022-07-18 11:47 ` Cornelia Huck [this message]
2022-07-19 3:08 ` [virtio-comment] Re: [External] " Lei He
2022-07-25 7:51 ` PING: " Lei He
2022-07-25 10:11 ` [virtio-comment] Re: [External] " Cornelia Huck
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=87r12iprq1.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=helei.sig11@bytedance.com \
--cc=mst@redhat.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