Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Carlos Maiolino <cem@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: "Darrick J. Wong" <djwong@kernel.org>, linux-xfs@vger.kernel.org
Subject: Re: small cleanups to help code sharing with xfsprogs
Date: Mon, 5 Oct 2026 12:02:51 +0200	[thread overview]
Message-ID: <asN1cm2BFRVilJtl@nidhogg.toxiclabs.cc> (raw)
In-Reply-To: <20260926060611.GC20636@lst.de>

Back from conferences. Sorry the late reply...

On Sat, Sep 26, 2026 at 08:06:11AM +0200, Christoph Hellwig wrote:
> On Fri, Sep 25, 2026 at 03:52:33PM -0700, Darrick J. Wong wrote:
> > On Fri, Sep 25, 2026 at 05:18:25PM +0200, Christoph Hellwig wrote:
> > > Hi all,
> > > 
> > > this series has a few trivial cleanups and code moves that help
> > > sharing more code with xfsprogs.
> > 
> > Hrmm.  This is a somewhat different approach than what Chris Wedgwood
> > did for his log port to userspace.
> 
> Well, that seems to have been an AI slop dump without any further
> engagement from the LLM-herder, so I'm not sure it matters.

Indeed, I'd stay with this series, so for this series:

Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>

> 
> But it also is a bit of a different thing.  This series tries to reduce
> the kernel/user libxfs differences, and reusing whatever we can from
> the kernel helps with that.  What we do about the log becomes relevant
> if/when we want to update that or share more.  My previously stated
> opinion is that splitting a single kernel code base into two libraries,
> which then generally are linked into the same programs again is not
> helpful.  But someone comes up with a design that actually makes it
> work painlessly I would not complain.  In the meantime I'd improve
> the maintainability of libxfs without touching the logging code at all.

Agreed.

  reply	other threads:[~2026-10-05 10:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 15:18 small cleanups to help code sharing with xfsprogs Christoph Hellwig
2026-09-25 15:18 ` [PATCH 1/4] xfs: remove various unused includes in libxfs/ Christoph Hellwig
2026-09-25 15:18 ` [PATCH 2/4] xfs: include <linux/iversion.h> in xfs_platform.h Christoph Hellwig
2026-09-25 15:18 ` [PATCH 3/4] xfs: move xfs_*_item.h to libxfs Christoph Hellwig
2026-09-25 15:18 ` [PATCH 4/4] xfs: move xfs_trans.h " Christoph Hellwig
2026-09-25 22:52 ` small cleanups to help code sharing with xfsprogs Darrick J. Wong
2026-09-26  6:06   ` Christoph Hellwig
2026-10-05 10:02     ` Carlos Maiolino [this message]
2026-10-08 13:32 ` Carlos Maiolino

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=asN1cm2BFRVilJtl@nidhogg.toxiclabs.cc \
    --to=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-xfs@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