linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
	linux-crypto@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH 1/7] lib/crc: remove unnecessary prompt for CONFIG_CRC32 and drop 'default y'
Date: Tue, 1 Apr 2025 21:50:57 -0700	[thread overview]
Message-ID: <81aac5ff-8698-4059-92a2-bccb998eb000@infradead.org> (raw)
In-Reply-To: <20250402035107.GA317606@sol.localdomain>



On 4/1/25 8:51 PM, Eric Biggers wrote:
> On Tue, Apr 01, 2025 at 08:42:41PM -0700, Randy Dunlap wrote:
>> Hi 
>>
>> On 4/1/25 3:15 PM, Eric Biggers wrote:
>>> From: Eric Biggers <ebiggers@google.com>
>>>
>>> All modules that need CONFIG_CRC32 already select it, so there is no
>>> need to bother users about the option, nor to default it to y.
>>>
>>
>> My memory from 10-20 years ago could be foggy, but ISTR that someone made at least
>> CRC16 and CRC32 user-selectable in order to support out-of-tree modules...
>> FWIW.
>> But they would not need to be default y.
> 
> That's not supported by upstream, though.

Which part is not supported by upstream?

-- 
~Randy


  reply	other threads:[~2025-04-02  4:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-01 22:15 [PATCH 0/7] More CRC kconfig option cleanups Eric Biggers
2025-04-01 22:15 ` [PATCH 1/7] lib/crc: remove unnecessary prompt for CONFIG_CRC32 and drop 'default y' Eric Biggers
2025-04-02  3:42   ` Randy Dunlap
2025-04-02  3:51     ` Eric Biggers
2025-04-02  4:50       ` Randy Dunlap [this message]
2025-04-02  5:02         ` Eric Biggers
2025-04-02  5:56           ` Randy Dunlap
2025-04-02 16:41             ` Eric Biggers
2025-04-04  8:36             ` Christoph Hellwig
2025-04-01 22:15 ` [PATCH 2/7] lib/crc: remove unnecessary prompt for CONFIG_CRC_CCITT Eric Biggers
2025-04-01 22:15 ` [PATCH 3/7] lib/crc: remove unnecessary prompt for CONFIG_CRC16 Eric Biggers
2025-04-01 22:15 ` [PATCH 4/7] lib/crc: remove unnecessary prompt for CONFIG_CRC_T10DIF Eric Biggers
2025-04-01 22:15 ` [PATCH 5/7] lib/crc: remove unnecessary prompt for CONFIG_CRC_ITU_T Eric Biggers
2025-04-01 22:15 ` [PATCH 6/7] lib/crc: document all the CRC library kconfig options Eric Biggers
2025-04-04  8:37   ` Christoph Hellwig
2025-04-04 19:02     ` Eric Biggers
2025-04-01 22:16 ` [PATCH 7/7] lib/crc: remove CONFIG_LIBCRC32C Eric Biggers
2025-04-02  6:47 ` [PATCH 0/7] More CRC kconfig option cleanups Ard Biesheuvel
2025-04-02 13:52 ` Martin K. Petersen
2025-04-04  8:37 ` Christoph Hellwig

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=81aac5ff-8698-4059-92a2-bccb998eb000@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=ardb@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=linux-arch@vger.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;
as well as URLs for NNTP newsgroup(s).