[PATCH 0/7] bcachefs out-of-tree series

Kent Overstreet posted 7 patches 2 months, 2 weeks ago
There is a newer version of this series
crypto/Kconfig                 |   2 +-
fs/bcachefs/alloc_foreground.h |   2 +-
fs/bcachefs/fs-io-direct.c     |   1 -
include/linux/closure.h        |  33 +++---
lib/Kconfig                    |  24 ++--
lib/closure.c                  | 203 +++++++++++++++++----------------
lib/crc/Kconfig                |   4 +-
lib/crypto/Kconfig             |   4 +-
8 files changed, 136 insertions(+), 137 deletions(-)
[PATCH 0/7] bcachefs out-of-tree series
Posted by Kent Overstreet 2 months, 2 weeks ago
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.

Also included is a bugfix patch series for closures for an issue with
unwinding closure_sync_timeout().

Kent Overstreet (7):
  closures: Improve closure_put_after_sub_checks
  closures: closure_sub() uses cmpxchg
  closures: CLOSURE_SLEEPING
  closures: kill closure.closure_get_happened
  lib: Give closures, min_heap config opts names
  lib: Give XOR_BLOCKS, RAID6_PQ config opts names
  lib: Give compression, checksum, crypto config opts names

 crypto/Kconfig                 |   2 +-
 fs/bcachefs/alloc_foreground.h |   2 +-
 fs/bcachefs/fs-io-direct.c     |   1 -
 include/linux/closure.h        |  33 +++---
 lib/Kconfig                    |  24 ++--
 lib/closure.c                  | 203 +++++++++++++++++----------------
 lib/crc/Kconfig                |   4 +-
 lib/crypto/Kconfig             |   4 +-
 8 files changed, 136 insertions(+), 137 deletions(-)

-- 
2.51.0
Re: [PATCH 0/7] bcachefs out-of-tree series
Posted by Christoph Hellwig 2 months, 2 weeks ago
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.