From: Marco Chiappero <marco.chiappero@intel.com>
To: herbert@gondor.apana.org.au
Cc: linux-crypto@vger.kernel.org, qat-linux@intel.com,
giovanni.cabiddu@intel.com,
Marco Chiappero <marco.chiappero@intel.com>,
kernel test robot <lkp@intel.com>
Subject: [PATCH] crypto: qat - add CRYPTO_AES to Kconfig dependencies
Date: Tue, 22 Dec 2020 13:00:24 +0000 [thread overview]
Message-ID: <20201222130024.694558-1-marco.chiappero@intel.com> (raw)
This patch includes a missing dependency (CRYPTO_AES) which may
lead to an "undefined reference to `aes_expandkey'" linking error.
Fixes: 5106dfeaeabe ("crypto: qat - add AES-XTS support for QAT GEN4 devices")
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Marco Chiappero <marco.chiappero@intel.com>
---
drivers/crypto/qat/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/crypto/qat/Kconfig b/drivers/crypto/qat/Kconfig
index beb379b23dc3..846a3d90b41a 100644
--- a/drivers/crypto/qat/Kconfig
+++ b/drivers/crypto/qat/Kconfig
@@ -11,6 +11,7 @@ config CRYPTO_DEV_QAT
select CRYPTO_SHA1
select CRYPTO_SHA256
select CRYPTO_SHA512
+ select CRYPTO_AES
select FW_LOADER
config CRYPTO_DEV_QAT_DH895xCC
--
2.26.2
next reply other threads:[~2020-12-22 12:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 13:00 Marco Chiappero [this message]
2020-12-23 7:51 ` [PATCH] crypto: qat - add CRYPTO_AES to Kconfig dependencies Herbert Xu
2020-12-23 18:39 ` Ard Biesheuvel
2020-12-23 20:57 ` Herbert Xu
2021-01-04 15:35 ` [PATCH] crypto: qat - replace CRYPTO_AES with CRYPTO_LIB_AES in Kconfig Marco Chiappero
2021-01-04 15:48 ` Ard Biesheuvel
2021-01-04 17:01 ` Giovanni Cabiddu
2021-01-14 6:46 ` Herbert Xu
2021-01-04 15:17 ` [PATCH] crypto: qat - add CRYPTO_AES to Kconfig dependencies Chiappero, Marco
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=20201222130024.694558-1-marco.chiappero@intel.com \
--to=marco.chiappero@intel.com \
--cc=giovanni.cabiddu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=lkp@intel.com \
--cc=qat-linux@intel.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).