linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Zaibo Xu <xuzaibo@huawei.com>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
	linux-crypto@vger.kernel.org, linuxarm@huawei.com,
	forest.zhouchang@huawei.com
Subject: Re: [PATCH 0/5] crypto: hisilicon - add HPRE support
Date: Thu, 10 Oct 2019 23:54:32 +1100	[thread overview]
Message-ID: <20191010125432.GC31566@gondor.apana.org.au> (raw)
In-Reply-To: <1569835209-44326-1-git-send-email-xuzaibo@huawei.com>

On Mon, Sep 30, 2019 at 05:20:04PM +0800, Zaibo Xu wrote:
> This series adds HiSilicon high performance RSA engine(HPRE) driver
> in crypto subsystem. HPRE driver provides PCIe hardware device initiation
> with RSA and DH algorithms registered to Crypto. Meanwhile, some debug
> supporting of DebugFS is given.
> 
> Zaibo Xu (5):
>   crypto: hisilicon - add HiSilicon HPRE accelerator
>   crypto: hisilicon - add SRIOV support for HPRE
>   Documentation: Add debugfs doc for hisi_hpre
>   crypto: hisilicon: Add debugfs for HPRE
>   MAINTAINERS: Add maintainer for HiSilicon HPRE driver
> 
>  Documentation/ABI/testing/debugfs-hisi-hpre |   57 ++
>  MAINTAINERS                                 |    9 +
>  drivers/crypto/hisilicon/Kconfig            |   11 +
>  drivers/crypto/hisilicon/Makefile           |    1 +
>  drivers/crypto/hisilicon/hpre/Makefile      |    2 +
>  drivers/crypto/hisilicon/hpre/hpre.h        |   83 ++
>  drivers/crypto/hisilicon/hpre/hpre_crypto.c | 1137 +++++++++++++++++++++++++++
>  drivers/crypto/hisilicon/hpre/hpre_main.c   | 1052 +++++++++++++++++++++++++
>  8 files changed, 2352 insertions(+)
>  create mode 100644 Documentation/ABI/testing/debugfs-hisi-hpre
>  create mode 100644 drivers/crypto/hisilicon/hpre/Makefile
>  create mode 100644 drivers/crypto/hisilicon/hpre/hpre.h
>  create mode 100644 drivers/crypto/hisilicon/hpre/hpre_crypto.c
>  create mode 100644 drivers/crypto/hisilicon/hpre/hpre_main.c

All applied.  Thanks.
-- 
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

      parent reply	other threads:[~2019-10-10 12:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-30  9:20 [PATCH 0/5] crypto: hisilicon - add HPRE support Zaibo Xu
2019-09-30  9:20 ` [PATCH 1/5] crypto: hisilicon - add HiSilicon HPRE accelerator Zaibo Xu
2019-10-15 20:13   ` [PATCH] crypto: hisilicon: Fix misuse of GENMASK macro Rikard Falkeborn
2019-10-16  1:34     ` Xu Zaibo
2019-10-18  8:07     ` Herbert Xu
2019-09-30  9:20 ` [PATCH 2/5] crypto: hisilicon - add SRIOV support for HPRE Zaibo Xu
2019-09-30  9:20 ` [PATCH 3/5] Documentation: Add debugfs doc for hisi_hpre Zaibo Xu
2019-09-30  9:20 ` [PATCH 4/5] crypto: hisilicon: Add debugfs for HPRE Zaibo Xu
2019-09-30  9:20 ` [PATCH 5/5] MAINTAINERS: Add maintainer for HiSilicon HPRE driver Zaibo Xu
2019-10-09  3:15 ` [PATCH 0/5] crypto: hisilicon - add HPRE support Xu Zaibo
2019-10-10 12:54 ` Herbert Xu [this message]

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=20191010125432.GC31566@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=davem@davemloft.net \
    --cc=forest.zhouchang@huawei.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=xuzaibo@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).