From: <dan.j.williams@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>,
<linux-kernel@vger.kernel.org>
Cc: <akpm@linux-foundation.org>,
Kent Overstreet <kent.overstreet@linux.dev>,
Eric Biggers <ebiggers@kernel.org>
Subject: Re: [PATCH 6/7] lib: Give XOR_BLOCKS, RAID6_PQ config opts names
Date: Wed, 8 Oct 2025 15:49:59 -0700 [thread overview]
Message-ID: <68e6ea973d318_2f89910066@dwillia2-mobl4.notmuch> (raw)
In-Reply-To: <20251004020049.918665-7-kent.overstreet@linux.dev>
Kent Overstreet wrote:
> Give these config options names so that they show up under the "Library
> routes" kernel configuration menu, and can be enabled by distributions.
A distribution specifies a kernel configuration. A distribution that
ships a given out-of-tree module can arrange for all its dependencies to
be met.
> These are needed for bcachefs to be built out of tree.
>
> These libraries are both for RAID5/6.
>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Eric Biggers <ebiggers@kernel.org>
> Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
> ---
> crypto/Kconfig | 2 +-
> lib/Kconfig | 4 +++-
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/crypto/Kconfig b/crypto/Kconfig
> index 23bd98981ae8..da4f072abae0 100644
> --- a/crypto/Kconfig
> +++ b/crypto/Kconfig
> @@ -3,7 +3,7 @@
> # Generic algorithms support
> #
> config XOR_BLOCKS
> - tristate
> + tristate "Accelerated block xor algorithm"
For example, the approach taken with the CXL unit test modules in
tools/testing/ is to have them assert all their dependencies.
Specifically, tools/testing/cxl/config_check.c validates the test
environment rather than giving the out-of-tree module the ability to
select symbols.
Now in this specific case of XOR_BLOCKS, if a distribution really wants
CONFIG_XOR_BLOCKS=n in its main config *and* wants to ship an
out-of-tree module that depends on CONFIG_XOR_BLOCKS=m, then that
distribution needs to provide an xor.ko to meet that dependency. Not
make upstream carry a patch to make that symbol configurable with no
upstream consumer.
tools/testing/cxl/Kbuild is an example of building a set of in-tree
modules as out-of-tree modules.
next prev parent reply other threads:[~2025-10-08 22:50 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
2025-10-08 22:49 ` dan.j.williams [this message]
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=68e6ea973d318_2f89910066@dwillia2-mobl4.notmuch \
--to=dan.j.williams@intel.com \
--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