From: Christoph Hellwig <hch@infradead.org>
To: Carlos Maiolino <cem@kernel.org>
Cc: aalbersh@kernel.org,
Wilfred Mallawa <wilfred.opensource@gmail.com>,
"Darrick J . Wong" <djwong@kernel.org>,
Alistair Francis <alistair.francis@wdc.com>,
Damien Le'Moal <dlemoal@kernel.org>,
linux-xfs@vger.kernel.org,
Wilfred Mallawa <wilfred.mallawa@wdc.com>
Subject: Re: [PATCH 1/3] xfs: add write pointer to xfs_rtgroup_geometry
Date: Tue, 22 Sep 2026 06:45:04 -0700 [thread overview]
Message-ID: <arKGYI0cMIEE_VAW@infradead.org> (raw)
In-Reply-To: <arKFdAhuxSq32e-P@nidhogg.toxiclabs.cc>
On Tue, Sep 22, 2026 at 03:41:59PM +0200, Carlos Maiolino wrote:
> On Tue, Sep 22, 2026 at 05:50:40AM -0700, Christoph Hellwig wrote:
> > It looks like patches 2 and 3 in this series never made it into
> > the xfsprogs repository despite being fully reviewed. Can we get them
> > picked up?
>
> Cc'ing Andrey here.
That might help indeed :)
next prev parent reply other threads:[~2026-09-22 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 0:24 [PATCH 1/3] xfs: add write pointer to xfs_rtgroup_geometry Wilfred Mallawa
2026-03-13 0:24 ` [PATCH 2/3] man/xfs_rtgroup_geometry: add rg_writepointer field description Wilfred Mallawa
2026-03-13 3:27 ` Darrick J. Wong
2026-03-16 9:04 ` Christoph Hellwig
2026-03-13 0:24 ` [PATCH 3/3] xfs_io: report rg_writepointer in report rg_info() Wilfred Mallawa
2026-03-13 3:28 ` Darrick J. Wong
2026-03-16 9:04 ` Christoph Hellwig
2026-09-22 12:50 ` [PATCH 1/3] xfs: add write pointer to xfs_rtgroup_geometry Christoph Hellwig
2026-09-22 13:41 ` Carlos Maiolino
2026-09-22 13:45 ` Christoph Hellwig [this message]
2026-09-22 14:01 ` Andrey Albershteyn
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=arKGYI0cMIEE_VAW@infradead.org \
--to=hch@infradead.org \
--cc=aalbersh@kernel.org \
--cc=alistair.francis@wdc.com \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=wilfred.mallawa@wdc.com \
--cc=wilfred.opensource@gmail.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