From: Herbert Xu <herbert@gondor.apana.org.au>
To: Zaibo Xu <xuzaibo@huawei.com>
Cc: davem@davemloft.net, linux-crypto@vger.kernel.org,
linuxarm@huawei.com, jonathan.cameron@huawei.com,
wangzhou1@hisilicon.com, tanghui20@huawei.com,
yekai13@huawei.com, liulongfang@huawei.com, qianweili@huawei.com,
zhangwei375@huawei.com, fanghao11@huawei.com,
forest.zhouchang@huawei.com
Subject: Re: [PATCH v2 0/9] crypto: hisilicon-SEC V2 AEAD added with some bugfixed
Date: Thu, 16 Jan 2020 15:29:18 +0800 [thread overview]
Message-ID: <20200116072918.emqpubgi3fxthpe4@gondor.apana.org.au> (raw)
In-Reply-To: <1578710516-40535-1-git-send-email-xuzaibo@huawei.com>
On Sat, Jan 11, 2020 at 10:41:47AM +0800, Zaibo Xu wrote:
> Add AEAD algorithms supporting, and some bugfixed with
> some updating on internal funcions to support more algorithms.
>
> This series is based on:
> git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git
>
> Change log:
> V2: Rebased on Arnd Bergmann's fixing patch on DebugFS usage.
>
> Zaibo Xu (9):
> crypto: hisilicon - Update debugfs usage of SEC V2
> crypto: hisilicon - fix print/comment of SEC V2
> crypto: hisilicon - Update some names on SEC V2
> crypto: hisilicon - Update QP resources of SEC V2
> crypto: hisilicon - Adjust some inner logic
> crypto: hisilicon - Add callback error check
> crypto: hisilicon - Add branch prediction macro
> crypto: hisilicon - redefine skcipher initiation
> crypto: hisilicon - Add aead support on SEC2
>
> drivers/crypto/hisilicon/Kconfig | 8 +-
> drivers/crypto/hisilicon/sec2/sec.h | 49 +-
> drivers/crypto/hisilicon/sec2/sec_crypto.c | 963 +++++++++++++++++++++++------
> drivers/crypto/hisilicon/sec2/sec_crypto.h | 22 +-
> drivers/crypto/hisilicon/sec2/sec_main.c | 23 +-
> 5 files changed, 833 insertions(+), 232 deletions(-)
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
prev parent reply other threads:[~2020-01-16 7:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 2:41 [PATCH v2 0/9] crypto: hisilicon-SEC V2 AEAD added with some bugfixed Zaibo Xu
2020-01-11 2:41 ` [PATCH v2 1/9] crypto: hisilicon - Update debugfs usage of SEC V2 Zaibo Xu
2020-01-11 2:41 ` [PATCH v2 2/9] crypto: hisilicon - fix print/comment " Zaibo Xu
2020-01-11 2:41 ` [PATCH v2 3/9] crypto: hisilicon - Update some names on " Zaibo Xu
2020-01-11 2:41 ` [PATCH v2 4/9] crypto: hisilicon - Update QP resources of " Zaibo Xu
2020-01-11 2:41 ` [PATCH v2 5/9] crypto: hisilicon - Adjust some inner logic Zaibo Xu
2020-01-11 2:41 ` [PATCH v2 6/9] crypto: hisilicon - Add callback error check Zaibo Xu
2020-01-11 2:41 ` [PATCH v2 7/9] crypto: hisilicon - Add branch prediction macro Zaibo Xu
2020-01-11 2:41 ` [PATCH v2 8/9] crypto: hisilicon - redefine skcipher initiation Zaibo Xu
2020-01-11 2:41 ` [PATCH v2 9/9] crypto: hisilicon - Add aead support on SEC2 Zaibo Xu
2020-01-16 7:29 ` 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=20200116072918.emqpubgi3fxthpe4@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=fanghao11@huawei.com \
--cc=forest.zhouchang@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liulongfang@huawei.com \
--cc=qianweili@huawei.com \
--cc=tanghui20@huawei.com \
--cc=wangzhou1@hisilicon.com \
--cc=xuzaibo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.