From: Longfang Liu <liulongfang@huawei.com>
To: <herbert@gondor.apana.org.au>, <wangzhou1@hisilicon.com>,
<xuzaibo@huawei.com>
Cc: <linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH 3/3] crypto: hisilicon/sec - fixes shash test error
Date: Fri, 5 Feb 2021 18:10:57 +0800 [thread overview]
Message-ID: <1612519857-30714-4-git-send-email-liulongfang@huawei.com> (raw)
In-Reply-To: <1612519857-30714-1-git-send-email-liulongfang@huawei.com>
If this configuration item is not turned on,
the allocation of crypto_tfm will fail when
the shash algorithm calculates the hash
through the software.
Signed-off-by: Longfang Liu <liulongfang@huawei.com>
---
arch/arm64/configs/defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 8383016..7cfc9b6 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -117,7 +117,7 @@ CONFIG_KVM=y
CONFIG_ARM64_CRYPTO=y
CONFIG_CRYPTO_SHA1_ARM64_CE=y
CONFIG_CRYPTO_SHA2_ARM64_CE=y
-CONFIG_CRYPTO_SHA512_ARM64_CE=m
+CONFIG_CRYPTO_SHA512_ARM64_CE=y
CONFIG_CRYPTO_SHA3_ARM64=m
CONFIG_CRYPTO_SM3_ARM64_CE=m
CONFIG_CRYPTO_GHASH_ARM64_CE=y
--
2.8.1
next prev parent reply other threads:[~2021-02-06 0:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 10:10 [PATCH 0/3] crypto:hisilicon/sec - fixes some coding style Longfang Liu
2021-02-05 10:10 ` [PATCH 1/3] crypto: hisilicon/sec - fixes some log printing style Longfang Liu
2021-02-05 10:10 ` [PATCH 2/3] crypto: hisilicon/sec - fixes some driver coding style Longfang Liu
2021-02-05 10:10 ` Longfang Liu [this message]
2021-02-05 11:44 ` [PATCH 3/3] crypto: hisilicon/sec - fixes shash test error Herbert Xu
2021-02-07 2:46 ` liulongfang
2021-02-07 8:02 ` Ard Biesheuvel
2021-02-07 9:49 ` liulongfang
2021-02-20 9:51 ` liulongfang
2021-03-04 4:41 ` Herbert Xu
2021-03-04 5:56 ` liulongfang
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=1612519857-30714-4-git-send-email-liulongfang@huawei.com \
--to=liulongfang@huawei.com \
--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®