From: "Darrick J. Wong" <djwong@kernel.org>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-xfs@vger.kernel.org, cem@kernel.org, hch@infradead.org
Subject: Re: [PATCH 0/2] xfs: share rmap & refcount btree ops
Date: Tue, 22 Sep 2026 16:26:06 -0700 [thread overview]
Message-ID: <20260922232606.GB2705364@frogsfrogsfrogs> (raw)
In-Reply-To: <20260922231845.3266784-1-sandeen@redhat.com>
On Tue, Sep 22, 2026 at 06:17:07PM -0500, Eric Sandeen wrote:
> The first patch should be what I sent before, just combinediff'd.
>
> The second patch does the same for the refcount btrees as suggested.
>
> I didn't keep prior RVBs since it's not the same patch any more...
>
> This elimiates almost 250 LOC.
Offhand that looks fine to me!
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
next prev parent reply other threads:[~2026-09-22 23:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 23:17 [PATCH 0/2] xfs: share rmap & refcount btree ops Eric Sandeen
2026-09-22 23:17 ` [PATCH 1/2] xfs: share the AG rmap btree with the rt rmap btree Eric Sandeen
2026-09-23 4:39 ` Christoph Hellwig
2026-09-22 23:17 ` [PATCH 2/2] xfs: share the AG refcount btree with the rt refcount btree Eric Sandeen
2026-09-23 4:39 ` Christoph Hellwig
2026-09-22 23:26 ` Darrick J. Wong [this message]
2026-10-05 18:06 ` [PATCH 0/2] xfs: share rmap & refcount btree ops 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=20260922232606.GB2705364@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
/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