From: Farhan Ali <alifm@linux.ibm.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Christian Borntraeger <borntraeger@de.ibm.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
mst@redhat.com, qemu-devel@nongnu.org, arei.gonglei@huawei.com,
longpeng2@huawei.com, pasic@linux.ibm.com, frankja@linux.ibm.com,
Jason Wang <jasowang@redhat.com>,
linux-crypto@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH v2 0/2] Detect & register virtio-crypto algos only if it can be supported by backend
Date: Tue, 19 Jun 2018 10:57:54 -0400 [thread overview]
Message-ID: <4301ac2e-a8f5-7432-cdd9-f39d30a9fb5e@linux.ibm.com> (raw)
In-Reply-To: <20180619143230.zjemmhhz7embs2li@gondor.apana.org.au>
On 06/19/2018 10:32 AM, Herbert Xu wrote:
> On Tue, Jun 19, 2018 at 04:08:05PM +0200, Christian Borntraeger wrote:
>> On 06/19/2018 03:26 PM, Farhan Ali wrote:
>>> A polite ping :)
>>>
>>> If no one has any more comments/feedback then I would like to how to merge these patches to the mainline kernel tree.
>>
>> I think it should go via Michael Tsirkin or Jason Wang (Adding Jason).
>> Also adding Herbert Xu as FYI.
>>
>>
>> I have not looked into the details of the patch, but I like the idea.
>> Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
>
> Please post crypto patches to linux-crypto.
>
> Thanks,
>
I have cc'ed linux-crypto folks. Sorry I missed them
Thanks
Farhan
next prev parent reply other threads:[~2018-06-19 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 20:38 [Qemu-devel] [PATCH v2 0/2] Detect & register virtio-crypto algos only if it can be supported by backend Farhan Ali
2018-06-13 20:38 ` [Qemu-devel] [PATCH v2 1/2] crypto/virtio-crypto: Read crypto services and algorithm masks Farhan Ali
2018-06-13 20:38 ` [Qemu-devel] [PATCH v2 2/2] crypto/virtio-crypto: Register an algo only if it's supported Farhan Ali
2018-06-19 13:26 ` [Qemu-devel] [PATCH v2 0/2] Detect & register virtio-crypto algos only if it can be supported by backend Farhan Ali
2018-06-19 14:08 ` Christian Borntraeger
2018-06-19 14:32 ` Herbert Xu
2018-06-19 14:57 ` Farhan Ali [this message]
2018-06-19 15:30 ` 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=4301ac2e-a8f5-7432-cdd9-f39d30a9fb5e@linux.ibm.com \
--to=alifm@linux.ibm.com \
--cc=arei.gonglei@huawei.com \
--cc=borntraeger@de.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longpeng2@huawei.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).