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 v2 3/3] crypto: hisilicon/sec - fixes shash test error
Date: Sun, 7 Feb 2021 18:04:40 +0800 [thread overview]
Message-ID: <1612692280-11386-4-git-send-email-liulongfang@huawei.com> (raw)
In-Reply-To: <1612692280-11386-1-git-send-email-liulongfang@huawei.com>
If the header file "crypto/internal/hash.h" not
added, 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>
---
drivers/crypto/hisilicon/sec2/sec_crypto.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/crypto/hisilicon/sec2/sec_crypto.c b/drivers/crypto/hisilicon/sec2/sec_crypto.c
index d2c4a2c..988faf7 100644
--- a/drivers/crypto/hisilicon/sec2/sec_crypto.c
+++ b/drivers/crypto/hisilicon/sec2/sec_crypto.c
@@ -7,6 +7,7 @@
#include <crypto/des.h>
#include <crypto/hash.h>
#include <crypto/internal/aead.h>
+#include <crypto/internal/hash.h>
#include <crypto/sha1.h>
#include <crypto/sha2.h>
#include <crypto/skcipher.h>
--
2.8.1
next prev parent reply other threads:[~2021-02-07 10:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 10:04 [PATCH v2 0/3] crypto:hisilicon/sec - fixes some coding style Longfang Liu
2021-02-07 10:04 ` [PATCH v2 1/3] crypto: hisilicon/sec - fixes some log printing style Longfang Liu
2021-02-07 10:04 ` [PATCH v2 2/3] crypto: hisilicon/sec - fixes some driver coding style Longfang Liu
2021-02-07 10:04 ` Longfang Liu [this message]
2021-02-10 6:43 ` [PATCH v2 3/3] crypto: hisilicon/sec - fixes shash test error Herbert Xu
2021-02-18 2:01 ` liulongfang
2021-02-18 2:06 ` Herbert Xu
2021-02-20 9:47 ` 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=1612692280-11386-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®