From: "Arnd Bergmann" <arnd@kernel.org>
To: "Fabio Estevam" <festevam@gmail.com>
Cc: "Herbert Xu" <herbert@gondor.apana.org.au>,
"Eric Biggers" <ebiggers@google.com>,
linux-arm-kernel@lists.infradead.org,
"Fabio Estevam" <festevam@denx.de>
Subject: Re: [PATCH] arm64: defconfig: Ensure CRYPTO_CHACHA20_NEON is selected
Date: Thu, 15 May 2025 17:24:09 +0200 [thread overview]
Message-ID: <ece2df8d-acaa-4554-8c82-24ed45f3a8a4@app.fastmail.com> (raw)
In-Reply-To: <20250515151548.431853-1-festevam@gmail.com>
On Thu, May 15, 2025, at 17:15, Fabio Estevam wrote:
> From: Fabio Estevam <festevam@denx.de>
>
> Since commit 17ec3e71ba79 ("crypto: lib/Kconfig - Hide arch options from
> user"), the CRYPTO_CHACHA20_NEON option is no longer selected by default
> due to changes in how crypto library options are exposed and selected.
>
> To restore the previous behavior and ensure CRYPTO_CHACHA20_NEON is
> enabled, explicitly select CONFIG_CRYPTO_CHACHA20 in the defconfig. This
> pulls in CRYPTO_LIB_CHACHA_INTERNAL and allows CRYPTO_CHACHA20_NEON to be
> selected automatically as before.
>
> Fixes: 17ec3e71ba79 ("crypto: lib/Kconfig - Hide arch options from user")
> Signed-off-by: Fabio Estevam <festevam@denx.de>
Acked-by: Arnd Bergmann <arnd@arndb.de>
in case Herbert wants to pick this up as a fix for the crypto tree,
or I can apply this through arm-soc if you send a copy to soc@lists.linux.dev.
Arnd
next prev parent reply other threads:[~2025-05-15 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 15:15 [PATCH] arm64: defconfig: Ensure CRYPTO_CHACHA20_NEON is selected Fabio Estevam
2025-05-15 15:24 ` Arnd Bergmann [this message]
2025-05-16 9:26 ` 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=ece2df8d-acaa-4554-8c82-24ed45f3a8a4@app.fastmail.com \
--to=arnd@kernel.org \
--cc=ebiggers@google.com \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox