From: Christoph Hellwig <hch@infradead.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Eric Biggers <ebiggers@kernel.org>
Subject: Re: [PATCH 0/7] bcachefs out-of-tree series
Date: Fri, 3 Oct 2025 21:15:54 -0700 [thread overview]
Message-ID: <aOCferuW5V61WMQZ@infradead.org> (raw)
In-Reply-To: <20251004020049.918665-1-kent.overstreet@linux.dev>
On Fri, Oct 03, 2025 at 10:00:42PM -0400, Kent Overstreet wrote:
> A few patches for out-of-tree bcachefs.
>
> Since bcachefs was dropped from mainline, the kconfig tweaks for lib/
> are needed for it to build out of tree; they just give a few config
> options names, so that distros can ensure they are enabled.
No. The Linux kernel is about in-tree stuff. There are not exports,
or especially Kconfigs that make things confusing for out of tree code.
Just like everyone else you'll have to live with what people do in-tree
for in-tree users.
prev parent reply other threads:[~2025-10-04 4:15 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
2025-10-04 2:00 ` [PATCH 7/7] lib: Give compression, checksum, crypto " Kent Overstreet
2025-10-04 4:15 ` Christoph Hellwig [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=aOCferuW5V61WMQZ@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