From: Eric Biggers <ebiggers@kernel.org>
To: Julian Braha <julianbraha@gmail.com>
Cc: herbert@gondor.apana.org.au, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, fazilyildiran@gmail.com
Subject: Re: [PATCH] crypto: fix CRYPTO_LIB_* dependencies on CRYPTO
Date: Mon, 5 Apr 2021 15:50:16 -0700 [thread overview]
Message-ID: <YGuUKBPHRqjmjdQd@gmail.com> (raw)
In-Reply-To: <20210405150438.177783-1-julianbraha@gmail.com>
On Mon, Apr 05, 2021 at 11:04:38AM -0400, Julian Braha wrote:
> Currently, when a config option selects a
> CRYPTO_LIB_* option while CRYPTO is disabled,
> Kbuild gives an unmet dependency. However,
> these config options do not actually need to
> depend on CRYPTO.
>
> Signed-off-by: Julian Braha <julianbraha@gmail.com>
> ---
> crypto/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/crypto/Kconfig b/crypto/Kconfig
> index 5809cc198fa7..fb7eca5cb8c6 100644
> --- a/crypto/Kconfig
> +++ b/crypto/Kconfig
> @@ -1870,9 +1870,9 @@ config CRYPTO_STATS
> config CRYPTO_HASH_INFO
> bool
>
> -source "lib/crypto/Kconfig"
> source "drivers/crypto/Kconfig"
> source "crypto/asymmetric_keys/Kconfig"
> source "certs/Kconfig"
>
> endif # if CRYPTO
> +source "lib/crypto/Kconfig"
> --
Actually some of the files in lib/crypto/ do depend on CRYPTO. For example,
there are calls to crypto_xor_cpy() and crypto_memneq(), which call functions
defined in crypto/algapi.c and crypto/memneq.c. These helper functions would
need to be moved into lib/crypto/ for this to work.
- Eric
prev parent reply other threads:[~2021-04-05 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 15:04 [PATCH] crypto: fix CRYPTO_LIB_* dependencies on CRYPTO Julian Braha
2021-04-05 22:50 ` Eric Biggers [this message]
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=YGuUKBPHRqjmjdQd@gmail.com \
--to=ebiggers@kernel.org \
--cc=fazilyildiran@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=julianbraha@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.