From: <Tudor.Ambarus@microchip.com>
To: <yuehaibing@huawei.com>, <herbert@gondor.apana.org.au>,
<davem@davemloft.net>, <cyrille.pitchen@atmel.com>
Cc: <linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 -next] crypto: atmel - Fix build error of CRYPTO_AUTHENC
Date: Tue, 12 Nov 2019 12:19:23 +0000 [thread overview]
Message-ID: <810b0a9b-d749-b351-18a3-234b3d7ae464@microchip.com> (raw)
In-Reply-To: <20191112072405.40268-1-yuehaibing@huawei.com>
On 11/12/2019 09:24 AM, YueHaibing wrote:
> If CRYPTO_DEV_ATMEL_AUTHENC is m, CRYPTO_DEV_ATMEL_SHA is m,
> but CRYPTO_DEV_ATMEL_AES is y, building will fails:
s/fails/fail
>
> drivers/crypto/atmel-aes.o: In function `atmel_aes_authenc_init_tfm':
> atmel-aes.c:(.text+0x670): undefined reference to `atmel_sha_authenc_get_reqsize'
> atmel-aes.c:(.text+0x67a): undefined reference to `atmel_sha_authenc_spawn'
> drivers/crypto/atmel-aes.o: In function `atmel_aes_authenc_setkey':
> atmel-aes.c:(.text+0x7e5): undefined reference to `atmel_sha_authenc_setkey'
>
> Make CRYPTO_DEV_ATMEL_AUTHENC depends on CRYPTO_DEV_ATMEL_AES,
s/depends/depend
> and select CRYPTO_DEV_ATMEL_SHA and CRYPTO_AUTHENC for it under there.
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Suggested-by: Herbert Xu <herbert@gondor.apana.org.au>
> Fixes: 89a82ef87e01 ("crypto: atmel-authenc - add support to...")
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
Reviewed-by: Tudor Ambarus <tudor.ambarus@microchip.com>
> ---
> v2: make CRYPTO_DEV_ATMEL_AUTHENC depends on DEV_ATMEL_AES
> ---
> drivers/crypto/Kconfig | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig
> index c5cc04d..296e829 100644
> --- a/drivers/crypto/Kconfig
> +++ b/drivers/crypto/Kconfig
> @@ -492,10 +492,9 @@ if CRYPTO_DEV_UX500
> endif # if CRYPTO_DEV_UX500
>
> config CRYPTO_DEV_ATMEL_AUTHENC
> - tristate "Support for Atmel IPSEC/SSL hw accelerator"
> + bool "Support for Atmel IPSEC/SSL hw accelerator"
> depends on ARCH_AT91 || COMPILE_TEST
> - select CRYPTO_DEV_ATMEL_AES
> - select CRYPTO_DEV_ATMEL_SHA
> + depends on CRYPTO_DEV_ATMEL_AES
> help
> Some Atmel processors can combine the AES and SHA hw accelerators
> to enhance support of IPSEC/SSL.
> @@ -507,8 +506,9 @@ config CRYPTO_DEV_ATMEL_AES
> depends on ARCH_AT91 || COMPILE_TEST
> select CRYPTO_AES
> select CRYPTO_AEAD
> - select CRYPTO_AUTHENC
> select CRYPTO_SKCIPHER
> + select CRYPTO_AUTHENC if CRYPTO_DEV_ATMEL_AUTHENC
> + select CRYPTO_DEV_ATMEL_SHA if CRYPTO_DEV_ATMEL_AUTHENC
> help
> Some Atmel processors have AES hw accelerator.
> Select this if you want to use the Atmel module for
>
next prev parent reply other threads:[~2019-11-12 12:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 13:39 [PATCH -next] crypto: atmel - Fix randbuild error YueHaibing
2019-11-12 2:13 ` Herbert Xu
2019-11-12 2:15 ` Herbert Xu
2019-11-12 11:56 ` Tudor.Ambarus
2019-11-12 12:16 ` Tudor.Ambarus
2019-11-12 7:24 ` [PATCH v2 -next] crypto: atmel - Fix build error of CRYPTO_AUTHENC YueHaibing
2019-11-12 12:19 ` Tudor.Ambarus [this message]
2019-11-13 9:55 ` [PATCH v3 " YueHaibing
2019-11-22 11:02 ` 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=810b0a9b-d749-b351-18a3-234b3d7ae464@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=cyrille.pitchen@atmel.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuehaibing@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®