From: Eric Biggers <ebiggers@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>
Subject: [PATCH 5/5] lib/crc: remove unnecessary prompt for CONFIG_CRC64
Date: Tue, 4 Mar 2025 15:07:12 -0800 [thread overview]
Message-ID: <20250304230712.167600-6-ebiggers@kernel.org> (raw)
In-Reply-To: <20250304230712.167600-1-ebiggers@kernel.org>
From: Eric Biggers <ebiggers@google.com>
All modules that need CONFIG_CRC64 already select it, so there is no
need to bother users about the option.
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
lib/Kconfig | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/lib/Kconfig b/lib/Kconfig
index 4bf2dd9f49a80..61cce0686b53e 100644
--- a/lib/Kconfig
+++ b/lib/Kconfig
@@ -192,16 +192,11 @@ config ARCH_HAS_CRC32
config CRC32_ARCH
tristate
default CRC32 if ARCH_HAS_CRC32 && CRC_OPTIMIZATIONS
config CRC64
- tristate "CRC64 functions"
- help
- This option is provided for the case where no in-kernel-tree
- modules require CRC64 functions, but a module built outside
- the kernel tree does. Such modules that use library CRC64
- functions require M here.
+ tristate
config ARCH_HAS_CRC64
bool
config CRC64_ARCH
--
2.48.1
next prev parent reply other threads:[~2025-03-04 23:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 23:07 [PATCH 0/5] Remove unnecessary prompts for CRC library (batch 1) Eric Biggers
2025-03-04 23:07 ` [PATCH 1/5] lib/crc: remove unnecessary prompt for CONFIG_CRC4 Eric Biggers
2025-03-04 23:07 ` [PATCH 2/5] lib/crc: remove unnecessary prompt for CONFIG_CRC7 Eric Biggers
2025-03-04 23:07 ` [PATCH 3/5] lib/crc: remove unnecessary prompt for CONFIG_CRC8 Eric Biggers
2025-03-04 23:07 ` [PATCH 4/5] lib/crc: remove unnecessary prompt for CONFIG_LIBCRC32C Eric Biggers
2025-03-04 23:07 ` Eric Biggers [this message]
2025-03-06 8:16 ` [PATCH 0/5] Remove unnecessary prompts for CRC library (batch 1) Ard Biesheuvel
2025-03-06 17:22 ` Eric Biggers
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=20250304230712.167600-6-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=ardb@kernel.org \
--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