From: Zhou Wang <wangzhou1@hisilicon.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: <davem@davemloft.net>, <linux-crypto@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linuxarm@huawei.com>
Subject: Re: [PATCH 0/5] crypto: hisilicon: Misc fixes
Date: Thu, 15 Aug 2019 22:00:11 +0800 [thread overview]
Message-ID: <5D55656B.6040907@hisilicon.com> (raw)
In-Reply-To: <20190815120838.GA29793@gondor.apana.org.au>
On 2019/8/15 20:08, Herbert Xu wrote:
> On Wed, Aug 14, 2019 at 05:28:34PM +0800, Zhou Wang wrote:
>> Patch 1~3 are fixes about kbuild errors, patch 4,5 are tiny fixes about qm
>> and zip.
>>
>> This series is based on cryptodev-2.6.
>>
>> Zhou Wang (5):
>> crypto: hisilicon - fix kbuild warnings
>> crypto: hisilicon - add dependency for CRYPTO_DEV_HISI_ZIP
>> crypto: hisilicon - init curr_sgl_dma to fix compile warning
>> crypto: hisilicon - add missing single_release
>> crypto: hisilicon - fix error handle in hisi_zip_create_req_q
>>
>> drivers/crypto/hisilicon/Kconfig | 1 +
>> drivers/crypto/hisilicon/qm.c | 7 ++++---
>> drivers/crypto/hisilicon/sgl.c | 2 +-
>> drivers/crypto/hisilicon/zip/zip_crypto.c | 6 ++++--
>> 4 files changed, 10 insertions(+), 6 deletions(-)
>
> All applied. Thanks.
>
Thanks for taking this series!
prev parent reply other threads:[~2019-08-15 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 9:28 [PATCH 0/5] crypto: hisilicon: Misc fixes Zhou Wang
2019-08-14 9:28 ` [PATCH 1/5] crypto: hisilicon - fix kbuild warnings Zhou Wang
2019-08-14 9:28 ` [PATCH 2/5] crypto: hisilicon - add dependency for CRYPTO_DEV_HISI_ZIP Zhou Wang
2019-08-14 9:28 ` [PATCH 3/5] crypto: hisilicon - init curr_sgl_dma to fix compile warning Zhou Wang
2019-08-14 9:28 ` [PATCH 4/5] crypto: hisilicon - add missing single_release Zhou Wang
2019-08-14 9:28 ` [PATCH 5/5] crypto: hisilicon - fix error handle in hisi_zip_create_req_q Zhou Wang
2019-08-15 12:08 ` [PATCH 0/5] crypto: hisilicon: Misc fixes Herbert Xu
2019-08-15 14:00 ` Zhou Wang [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=5D55656B.6040907@hisilicon.com \
--to=wangzhou1@hisilicon.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@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).