From: Kai Ye <yekai13@huawei.com>
To: <herbert@gondor.apana.org.au>
Cc: <linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<yekai13@huawei.com>
Subject: [PATCH v3 0/5] bug fix and clear coding style
Date: Fri, 9 Apr 2021 17:03:59 +0800 [thread overview]
Message-ID: <1617959044-11023-1-git-send-email-yekai13@huawei.com> (raw)
Fixup coding style such as delete unneeded variable
initialization. Add a comment for block size initialization.
Add a data cleared operation in sg buf unmap, and other misc fix.
v1 -> v2:
1. fix [PATCH v2] error in v1.
2. v1 use a macro replace of magic number, v2 use a comment
for block size initialization.
v2 -> v3:
fix a sparse warning
Kai Ye (5):
crypto: hisilicon/sgl - add a comment for block size initialization
crypto: hisilicon/sgl - delete unneeded variable initialization
crypto: hisilicon/sgl - add some dfx logs
crypto: hisilicon/sgl - fix the soft sg map to hardware sg
crypto: hisilicon/sgl - fix the sg buf unmap
drivers/crypto/hisilicon/sgl.c | 37 +++++++++++++++++++++++++++++++------
1 file changed, 31 insertions(+), 6 deletions(-)
--
2.8.1
next reply other threads:[~2021-04-09 9:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 9:03 Kai Ye [this message]
2021-04-09 9:04 ` [PATCH v3 1/5] crypto: hisilicon/sgl - add a comment for block size initialization Kai Ye
2021-04-09 9:04 ` [PATCH v3 2/5] crypto: hisilicon/sgl - delete unneeded variable initialization Kai Ye
2021-04-09 9:04 ` [PATCH v3 3/5] crypto: hisilicon/sgl - add some dfx logs Kai Ye
2021-04-09 9:04 ` [PATCH v3 4/5] crypto: hisilicon/sgl - fix the soft sg map to hardware sg Kai Ye
2021-04-09 9:04 ` [PATCH v3 5/5] crypto: hisilicon/sgl - fix the sg buf unmap Kai Ye
2021-04-16 11:32 ` [PATCH v3 0/5] bug fix and clear coding style 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=1617959044-11023-1-git-send-email-yekai13@huawei.com \
--to=yekai13@huawei.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).