From: "Michael S. Tsirkin" <mst@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "Gonglei (Arei)" <arei.gonglei@huawei.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
Luonengjun <luonengjun@huawei.com>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"Huangweidong (C)" <weidong.huang@huawei.com>,
"Wubin (H)" <wu.wubin@huawei.com>,
"xin.zeng@intel.com" <xin.zeng@intel.com>,
Claudio Fontana <Claudio.Fontana@huawei.com>,
"pasic@linux.vnet.ibm.com" <pasic@linux.vnet.ibm.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"Zhoujian (jay, Euler)" <jianjay.zhou@huawei.c
Subject: Re: [PATCH v6 2/2] crypto: add virtio-crypto driver
Date: Tue, 13 Dec 2016 00:05:19 +0200 [thread overview]
Message-ID: <20161212234941-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20161212105407.GA3033@gondor.apana.org.au>
On Mon, Dec 12, 2016 at 06:54:07PM +0800, Herbert Xu wrote:
> On Mon, Dec 12, 2016 at 06:25:12AM +0000, Gonglei (Arei) wrote:
> > Hi, Michael & Herbert
> >
> > Because the virtio-crypto device emulation had been in QEMU 2.8,
> > would you please merge the virtio-crypto driver for 4.10 if no other
> > comments? If so, Miachel pls ack and/or review the patch, then
> > Herbert will take it (I asked him last week). Thank you!
> >
> > Ps: Note on 4.10 merge window timing from Linus
> > https://lkml.org/lkml/2016/12/7/506
> >
> > Dec 23rd is the deadline for 4.10 merge window.
>
> Sorry but it's too late for 4.10. It needed to have been in my
> tree before the merge window opened to make it for this cycle.
>
> Cheers,
Objections to me merging this? I'm preparing my tree right now.
> --
> Email: Herbert Xu <herbert@gondor.apana.org.au>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2016-12-12 22:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 4:37 [PATCH v6 0/2] virtio-crypto: add Linux driver Gonglei
2016-12-08 4:37 ` [PATCH v6 1/2] sparc: fix a building error reported by kbuild Gonglei
2016-12-09 21:58 ` Sam Ravnborg
2016-12-10 8:40 ` Gonglei (Arei)
2016-12-22 14:58 ` Anatoly Pugachev
2016-12-08 4:37 ` [PATCH v6 2/2] crypto: add virtio-crypto driver Gonglei
2016-12-12 6:25 ` Gonglei (Arei)
2016-12-12 10:54 ` Herbert Xu
2016-12-12 22:05 ` Michael S. Tsirkin [this message]
2016-12-13 1:13 ` Gonglei (Arei)
2016-12-13 3:33 ` Herbert Xu
2016-12-13 16:11 ` Halil Pasic
2016-12-14 11:32 ` Gonglei (Arei)
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=20161212234941-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=Claudio.Fontana@huawei.com \
--cc=arei.gonglei@huawei.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jianjay.zhou@huawei.c \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luonengjun@huawei.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=weidong.huang@huawei.com \
--cc=wu.wubin@huawei.com \
--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;
as well as URLs for NNTP newsgroup(s).