From: Kai Ye <yekai13@huawei.com>
To: <herbert@gondor.apana.org.au>
Cc: <linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<wangzhou1@hisilicon.com>, <yekai13@huawei.com>
Subject: [PATCH v3 0/2] crypto: hisilicon - some misc bugfix for SEC engine
Date: Fri, 13 Aug 2021 10:21:25 +0800 [thread overview]
Message-ID: <1628821287-49924-1-git-send-email-yekai13@huawei.com> (raw)
some misc bugfix for SEC engine.
changes v1->v2:
delete the "ifdefs", use the IS_ENABLED.
changes v2->v3:
fix merge conflict
Kai Ye (2):
crypto: hisilicon/sec - fix the abnormal exiting process
crypto: hisilicon/sec - modify the hardware endian configuration
drivers/crypto/hisilicon/sec2/sec.h | 5 -----
drivers/crypto/hisilicon/sec2/sec_main.c | 34 +++++++++++---------------------
2 files changed, 11 insertions(+), 28 deletions(-)
--
2.7.4
next reply other threads:[~2021-08-13 2:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 2:21 Kai Ye [this message]
2021-08-13 2:21 ` [PATCH v3 1/2] crypto: hisilicon/sec - fix the abnormal exiting process Kai Ye
2021-08-13 2:21 ` [PATCH v3 2/2] crypto: hisilicon/sec - modify the hardware endian configuration Kai Ye
2021-08-13 5:34 ` kernel test robot
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=1628821287-49924-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 \
--cc=wangzhou1@hisilicon.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).