From: Eric Biggers <ebiggers@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH 0/5] Remove unnecessary prompts for CRC library (batch 1)
Date: Thu, 6 Mar 2025 09:22:28 -0800 [thread overview]
Message-ID: <20250306172228.GE1796@sol.localdomain> (raw)
In-Reply-To: <20250304230712.167600-1-ebiggers@kernel.org>
On Tue, Mar 04, 2025 at 03:07:07PM -0800, Eric Biggers wrote:
> Library functions are already selected when they are needed, so there is
> no need to ask users whether to enable them or not. This patchset fixes
> this for the first batch of CRC library options.
>
> There will be a batch 2 later to handle the rest.
>
> Eric Biggers (5):
> lib/crc: remove unnecessary prompt for CONFIG_CRC4
> lib/crc: remove unnecessary prompt for CONFIG_CRC7
> lib/crc: remove unnecessary prompt for CONFIG_CRC8
> lib/crc: remove unnecessary prompt for CONFIG_LIBCRC32C
> lib/crc: remove unnecessary prompt for CONFIG_CRC64
>
Applied to
https://web.git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=crc-next
- Eric
prev parent reply other threads:[~2025-03-06 17:22 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 ` [PATCH 5/5] lib/crc: remove unnecessary prompt for CONFIG_CRC64 Eric Biggers
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 [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=20250306172228.GE1796@sol.localdomain \
--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 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.