From: Christoph Hellwig <hch@infradead.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Eric Biggers <ebiggers@kernel.org>
Subject: Re: [PATCH 6/7] lib: Give XOR_BLOCKS, RAID6_PQ config opts names
Date: Fri, 3 Oct 2025 21:42:41 -0700 [thread overview]
Message-ID: <aOClwR1pOQodIBwC@infradead.org> (raw)
In-Reply-To: <ri6hb5q3i4t5jdfahmyp5wox3fqlyndnu3vfpsiqr7zbci7j6f@un5xm2rcokld>
On Sat, Oct 04, 2025 at 12:37:21AM -0400, Kent Overstreet wrote:
> On Fri, Oct 03, 2025 at 09:32:25PM -0700, Christoph Hellwig wrote:
> > On Sat, Oct 04, 2025 at 12:29:15AM -0400, Kent Overstreet wrote:
> > > That's been the primary purpose of the lib/ kconfig menu. The current
> > > language is no longer quite as explicit as it used to be, but here's a
> > > recent example:
> >
> > It's not the current kernel where this got fixed. If you find others
> > instances, we can fix them as well.
>
> The current language is only slightly less explicit, but the underlying
> purpose remains the same.
There is no such current language. It is a non-selectable symbol with
this standard help text used by all CRC helpers:
The CRC16 library functions. Select this if your module uses
any of the functions from <linux/crc16.h>.
next prev parent reply other threads:[~2025-10-04 4:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-04 2:00 [PATCH 0/7] bcachefs out-of-tree series Kent Overstreet
2025-10-04 2:00 ` [PATCH 1/7] closures: Improve closure_put_after_sub_checks Kent Overstreet
2025-10-04 2:00 ` [PATCH 2/7] closures: closure_sub() uses cmpxchg Kent Overstreet
2025-10-04 2:00 ` [PATCH 3/7] closures: CLOSURE_SLEEPING Kent Overstreet
2025-10-04 2:00 ` [PATCH 4/7] closures: kill closure.closure_get_happened Kent Overstreet
2025-10-04 2:00 ` [PATCH 5/7] lib: Give closures, min_heap config opts names Kent Overstreet
2025-10-04 2:00 ` [PATCH 6/7] lib: Give XOR_BLOCKS, RAID6_PQ " Kent Overstreet
2025-10-04 4:14 ` Christoph Hellwig
2025-10-04 4:29 ` Kent Overstreet
2025-10-04 4:32 ` Christoph Hellwig
2025-10-04 4:37 ` Kent Overstreet
2025-10-04 4:42 ` Christoph Hellwig [this message]
2025-10-08 22:49 ` dan.j.williams
2025-10-04 2:00 ` [PATCH 7/7] lib: Give compression, checksum, crypto " Kent Overstreet
2025-10-04 4:15 ` [PATCH 0/7] bcachefs out-of-tree series 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=aOClwR1pOQodIBwC@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=ebiggers@kernel.org \
--cc=kent.overstreet@linux.dev \
--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