From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Eric Biggers <ebiggers@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/5] crypto: Drop stale usages in various help texts
Date: Thu, 26 Feb 2026 15:46:04 +0100 [thread overview]
Message-ID: <cover.1772116160.git.geert+renesas@glider.be> (raw)
Hi all,
This patch series drops stale references to subsystems that are using
various crypto algoritms. It was triggered by "make oldconfig" in
v7.0-rc1 showing new prompts about BLAKE2b, SHA-256, xxHash, and CRC32c
algorithms. When querying these symbols, the corresponding help texts
incorrectly claim they are used by btrfs.
Notw that even if correct, there is no need for such references, as all
users should select the needed symbols anyway.
Geert Uytterhoeven (5):
crypto: Drop stale CRYPTO_BLAKE2B usage
crypto: Drop stale CRYPTO_SHA256 usage
crypto: Drop stale CRYPTO_XXHASH usage
crypto: Drop stale CRYPTO_CRC32C usage
crypto: Drop stale CRYPTO_CRC32 usage
crypto/Kconfig | 9 ---------
1 file changed, 9 deletions(-)
--
2.43.0
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2026-02-26 14:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 14:46 Geert Uytterhoeven [this message]
2026-02-26 14:46 ` [PATCH 1/5] crypto: Clean up CRYPTO_BLAKE2B usage Geert Uytterhoeven
2026-02-26 14:46 ` [PATCH 2/5] crypto: Clean up CRYPTO_SHA256 usage Geert Uytterhoeven
2026-02-26 14:46 ` [PATCH 3/5] crypto: Clean up CRYPTO_XXHASH usage Geert Uytterhoeven
2026-02-26 14:46 ` [PATCH 4/5] crypto: Clean up CRYPTO_CRC32C usage Geert Uytterhoeven
2026-02-26 14:46 ` [PATCH 5/5] crypto: Clean up CRYPTO_CRC32 usage Geert Uytterhoeven
2026-02-26 19:54 ` [PATCH 0/5] crypto: Drop stale usages in various help texts Eric Biggers
2026-03-02 23:41 ` Eric Biggers
2026-03-03 7:57 ` Geert Uytterhoeven
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=cover.1772116160.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox