From: Xu Zaibo <xuzaibo@huawei.com>
To: <herbert@gondor.apana.org.au>, <davem@davemloft.net>
Cc: <forest.zhouchang@huawei.com>, <linuxarm@huawei.com>,
<zhangwei375@huawei.com>, <yekai13@huawei.com>,
<linux-crypto@vger.kernel.org>
Subject: Re: [PATCH v3 0/5] crypto: hisilicon - add HiSilicon SEC V2 support
Date: Wed, 20 Nov 2019 20:19:19 +0800 [thread overview]
Message-ID: <038b55c4-afc7-f69b-add8-fc94d5148630@huawei.com> (raw)
In-Reply-To: <1573643468-1812-1-git-send-email-xuzaibo@huawei.com>
Hi,
On 2019/11/13 19:11, Zaibo Xu wrote:
> This series adds HiSilicon Security Engine (SEC) version 2 controller
> driver in Crypto subsystem. It includes PCIe enabling, Skcipher, DebugFS
> and SRIOV support of SEC.
>
> This patchset rebases on:
> git://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git
>
> This patchset is based on:
> https://www.spinics.net/lists/linux-crypto/msg43520.html
>
> Changes on v3:
> - bugfixed as running CRYPTO extra tests.
>
> Changes on v2:
> - delete checking return value of debugfs_create_xxx functions.
>
> Change log:
> v3: - bugfixed as running CRTPTO extra tests.
> v2: - remove checking return value of debugfs_create_xxx functions.
>
> Longfang Liu (1):
> Documentation: add DebugFS doc for HiSilicon SEC
>
> Zaibo Xu (4):
> crypto: hisilicon - add HiSilicon SEC V2 driver
> crypto: hisilicon - add SRIOV for HiSilicon SEC
> crypto: hisilicon - add DebugFS for HiSilicon SEC
> MAINTAINERS: Add maintainer for HiSilicon SEC V2 driver
>
> Documentation/ABI/testing/debugfs-hisi-sec | 43 ++
> MAINTAINERS | 10 +
> drivers/crypto/hisilicon/Kconfig | 16 +
> drivers/crypto/hisilicon/Makefile | 1 +
> drivers/crypto/hisilicon/sec2/Makefile | 2 +
> drivers/crypto/hisilicon/sec2/sec.h | 156 ++++
> drivers/crypto/hisilicon/sec2/sec_crypto.c | 889 ++++++++++++++++++++++
> drivers/crypto/hisilicon/sec2/sec_crypto.h | 198 +++++
> drivers/crypto/hisilicon/sec2/sec_main.c | 1095 ++++++++++++++++++++++++++++
> 9 files changed, 2410 insertions(+)
> create mode 100644 Documentation/ABI/testing/debugfs-hisi-sec
> create mode 100644 drivers/crypto/hisilicon/sec2/Makefile
> create mode 100644 drivers/crypto/hisilicon/sec2/sec.h
> create mode 100644 drivers/crypto/hisilicon/sec2/sec_crypto.c
> create mode 100644 drivers/crypto/hisilicon/sec2/sec_crypto.h
> create mode 100644 drivers/crypto/hisilicon/sec2/sec_main.c
Any comments for this version?
Cheers,
Zaibo
next prev parent reply other threads:[~2019-11-20 12:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 11:11 [PATCH v3 0/5] crypto: hisilicon - add HiSilicon SEC V2 support Zaibo Xu
2019-11-13 11:11 ` [PATCH v3 1/5] crypto: hisilicon - add HiSilicon SEC V2 driver Zaibo Xu
2019-12-03 12:01 ` Marco Elver
2019-12-04 1:10 ` Xu Zaibo
2019-11-13 11:11 ` [PATCH v3 2/5] crypto: hisilicon - add SRIOV for HiSilicon SEC Zaibo Xu
2019-11-13 11:11 ` [PATCH v3 3/5] Documentation: add DebugFS doc " Zaibo Xu
2019-11-13 11:11 ` [PATCH v3 4/5] crypto: hisilicon - add DebugFS " Zaibo Xu
2019-12-03 12:12 ` Marco Elver
2019-12-04 1:12 ` Xu Zaibo
2019-11-13 11:11 ` [PATCH v3 5/5] MAINTAINERS: Add maintainer for HiSilicon SEC V2 driver Zaibo Xu
2019-11-20 12:19 ` Xu Zaibo [this message]
2019-11-22 11:03 ` [PATCH v3 0/5] crypto: hisilicon - add HiSilicon SEC V2 support Herbert Xu
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=038b55c4-afc7-f69b-add8-fc94d5148630@huawei.com \
--to=xuzaibo@huawei.com \
--cc=davem@davemloft.net \
--cc=forest.zhouchang@huawei.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=yekai13@huawei.com \
--cc=zhangwei375@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).