From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>
Cc: "Michael S. Tsirkin" <mst@redhat.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>,
"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>,
"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"pasic@linux.vnet.ibm.com" <pasic@linux.vnet.ibm.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"Zhoujian (jay, Euler)" <jianjay.zhou@huawei.com>,
"Hanweidong (Randy)" <hanweidong@huawei.com>,
"arei.gonglei@hotmail.com" <arei.gonglei@hotmail.com>,
"cornelia.huck@de.ibm.com" <cornelia.huck@de.ibm.com>,
"Xuquan (Quan Xu)" <xuquan8@huawei.com>,
longpeng <longpeng2@huawei.com>,
"salvatore.benedetto@intel.com" <salvatore.benedetto@intel.com>
Subject: Re: [Qemu-devel] [PATCH v3] crypto: add virtio-crypto driver
Date: Tue, 29 Nov 2016 09:25:49 +0000 [thread overview]
Message-ID: <20161129092549.GC5152@stefanha-x1.localdomain> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF19020DA14A7A9@DGGEMA505-MBX.china.huawei.com>
[-- Attachment #1: Type: text/plain, Size: 2123 bytes --]
On Tue, Nov 29, 2016 at 08:22:58AM +0000, Gonglei (Arei) wrote:
> Hi,
>
> > > > > +source "drivers/crypto/virtio/Kconfig"
> > > > > +
> > > > > endif # CRYPTO_HW
> > > > > diff --git a/drivers/crypto/Makefile b/drivers/crypto/Makefile
> > > > > index ad7250f..bc53cb8 100644
> > > > > --- a/drivers/crypto/Makefile
> > > > > +++ b/drivers/crypto/Makefile
> > > > > @@ -32,3 +32,4 @@ obj-$(CONFIG_CRYPTO_DEV_VMX) += vmx/
> > > > > obj-$(CONFIG_CRYPTO_DEV_SUN4I_SS) += sunxi-ss/
> > > > > obj-$(CONFIG_CRYPTO_DEV_ROCKCHIP) += rockchip/
> > > > > obj-$(CONFIG_CRYPTO_DEV_CHELSIO) += chelsio/
> > > > > +obj-$(CONFIG_CRYPTO_DEV_VIRTIO) += virtio/
> > > > > diff --git a/drivers/crypto/virtio/Kconfig b/drivers/crypto/virtio/Kconfig
> > > > > new file mode 100644
> > > > > index 0000000..ceae88c
> > > > > --- /dev/null
> > > > > +++ b/drivers/crypto/virtio/Kconfig
> > > > > @@ -0,0 +1,10 @@
> > > > > +config CRYPTO_DEV_VIRTIO
> > > > > + tristate "VirtIO crypto driver"
> > > > > + depends on VIRTIO
> > > > > + select CRYPTO_AEAD
> > > > > + select CRYPTO_AUTHENC
> > > > > + select CRYPTO_BLKCIPHER
> > > >
> > > > Inconsistent tab vs space whitespace usage.
> > > >
> > Will fix.
> >
> > > > > + default m
> > > > > + help
> > > > > + This driver provides support for virtio crypto device. If you
> > > > > + choose 'M' here, this module will be called virtio-crypto.
> > > >
> > > > All the other virtio drivers use underscore ('_') instead of hyphen
> > > > ('-').
> > >
> > > Except virtio-rng.
> > >
> > > > I suggest calling it virtio_crypto for consistency.
> > > >
> > OK, I will change the Makefile to fix it.
> >
>
> I tried to do this, but I failed. Because virtio_crypto.ko
> consists of more than one source file which include tree files currently,
> and virtio_crypto.ko matchs the name of virtio_crypto.c.
> That's different with all other virtio drivers.
Can you rename virtio_crypto.c to virtio_crypto_core.c?
I'm not very familiar with the kernel Makefile infrastructure so maybe
there's a better way of doing it.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2016-11-29 9:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 12:08 [Qemu-devel] [PATCH v3] virtio-crypto: add Linux driver Gonglei
2016-11-28 12:08 ` [Qemu-devel] [PATCH v3] crypto: add virtio-crypto driver Gonglei
2016-11-28 13:12 ` Cornelia Huck
2016-11-29 1:37 ` [Qemu-devel] [virtio-dev] " Gonglei (Arei)
2016-11-29 9:44 ` Cornelia Huck
2016-11-29 11:50 ` Gonglei (Arei)
2016-11-28 16:02 ` [Qemu-devel] " kbuild test robot
2016-11-28 16:20 ` Stefan Hajnoczi
2016-11-28 17:19 ` Michael S. Tsirkin
2016-11-28 17:37 ` Halil Pasic
2016-11-29 3:40 ` Gonglei (Arei)
2016-11-29 3:32 ` Gonglei (Arei)
2016-11-29 6:47 ` Gonglei (Arei)
2016-11-29 8:22 ` Gonglei (Arei)
2016-11-29 9:25 ` Stefan Hajnoczi [this message]
2016-11-29 9:29 ` Cornelia Huck
2016-11-29 11:46 ` Gonglei (Arei)
2016-11-29 9:31 ` 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=20161129092549.GC5152@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=Claudio.Fontana@huawei.com \
--cc=arei.gonglei@hotmail.com \
--cc=arei.gonglei@huawei.com \
--cc=cornelia.huck@de.ibm.com \
--cc=davem@davemloft.net \
--cc=hanweidong@huawei.com \
--cc=herbert@gondor.apana.org.au \
--cc=jianjay.zhou@huawei.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longpeng2@huawei.com \
--cc=luonengjun@huawei.com \
--cc=mst@redhat.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=salvatore.benedetto@intel.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 \
--cc=xuquan8@huawei.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).