From: Yang Shen <shenyang39@huawei.com>
To: <herbert@gondor.apana.org.au>, <davem@davemloft.net>
Cc: <linux-kernel@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
<xuzaibo@huawei.com>, <wangzhou1@hisilicon.com>
Subject: [PATCH RESEND 0/4] crypto: hisilicon/zip - misc clean up
Date: Fri, 25 Sep 2020 22:06:13 +0800 [thread overview]
Message-ID: <1601042777-26150-1-git-send-email-shenyang39@huawei.com> (raw)
This patchset fix some bug:
patch 1:clear the debug registers when remove driver
patch 2:intercept invalid input when using decompress
patch 3:replace the return value '-EBUSY' with '-EAGAIN' when
device is busy
patch 4:initialize the 'curr_qm_qp_num' when probe device
Resend this patch series because it depends on
https://patchwork.kernel.org/cover/11760159/
(crypto: hisilicon/zip - misc clean up).
Now the patch series has been applied.
Hao Fang (1):
crypto: hisilicon/zip - fix the uncleared debug registers
Sihang Chen (1):
crypto: hisilicon/zip - fix the uninitalized 'curr_qm_qp_num'
Yang Shen (1):
crypto: hisilicon/zip - fix the return value when device is busy
Zhou Wang (1):
crypto: hisilicon/zip - fix zero length input in GZIP decompress
drivers/crypto/hisilicon/zip/zip_crypto.c | 26 +++++++++++++++++++-------
drivers/crypto/hisilicon/zip/zip_main.c | 19 +++++++++++++++++++
2 files changed, 38 insertions(+), 7 deletions(-)
--
2.7.4
next reply other threads:[~2020-09-25 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 14:06 Yang Shen [this message]
2020-09-25 14:06 ` [PATCH RESEND 1/4] crypto: hisilicon/zip - fix the uncleared debug registers Yang Shen
2020-09-25 14:06 ` [PATCH RESEND 2/4] crypto: hisilicon/zip - fix zero length input in GZIP decompress Yang Shen
2020-09-25 14:06 ` [PATCH RESEND 3/4] crypto: hisilicon/zip - fix the return value when device is busy Yang Shen
2020-09-25 14:06 ` [PATCH RESEND 4/4] crypto: hisilicon/zip - fix the uninitalized 'curr_qm_qp_num' Yang Shen
2020-10-02 11:55 ` [PATCH RESEND 0/4] crypto: hisilicon/zip - misc clean up 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=1601042777-26150-1-git-send-email-shenyang39@huawei.com \
--to=shenyang39@huawei.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangzhou1@hisilicon.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
all inboxes | Powered by JetHome®