From: Niklas Cassel <cassel@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Carlos Maiolino <cem@kernel.org>,
Damien Le Moal <dlemoal@kernel.org>,
Hans Holmberg <hans.holmberg@wdc.com>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 4/4] xfs: untangle the open zones reporting in mountinfo
Date: Mon, 30 Mar 2026 11:55:01 +0200 [thread overview]
Message-ID: <acpIdXHqg_Y7bHEY@ryzen> (raw)
In-Reply-To: <20260330054732.GA5079@lst.de>
On Mon, Mar 30, 2026 at 07:47:32AM +0200, Christoph Hellwig wrote:
> Note that this patch actually requires the "cleanup open GC zone handling"
> series. I had the two the other way around in my local tree, but decided
> to send the series with the fix out first after a trivial rebase worked
> fine, which obviously wasn't a good enough test. Sorry.
I don't know if this series should be applied to 7.0 or not, but if so,
then I'm guessing that we do not want this series to depend on a cleanup
series.
If both series are targeting 7.1, then it probably doesn't matter.
Side note: You probably know this already, but if you had it the other way
around in your local tree, "git reflog" can be of great help to get the
SHA1 of the commit before the trivial rebase, even if you no longer have
any references to that old SHA1.
Kind regards,
Niklas
next prev parent reply other threads:[~2026-03-30 9:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 5:40 fix handling of too many open zones at mount time Christoph Hellwig
2026-03-30 5:40 ` [PATCH 1/4] xfs: refactor xfs_mount_zones Christoph Hellwig
2026-03-30 5:40 ` [PATCH 2/4] xfs: handle too many open zones when mounting Christoph Hellwig
2026-03-30 5:40 ` [PATCH 3/4] xfs: expose the number of open zones in sysfs Christoph Hellwig
2026-03-30 5:41 ` [PATCH 4/4] xfs: untangle the open zones reporting in mountinfo Christoph Hellwig
2026-03-30 5:47 ` Christoph Hellwig
2026-03-30 9:55 ` Niklas Cassel [this message]
2026-03-30 13:10 ` Christoph Hellwig
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=acpIdXHqg_Y7bHEY@ryzen \
--to=cassel@kernel.org \
--cc=cem@kernel.org \
--cc=dlemoal@kernel.org \
--cc=hans.holmberg@wdc.com \
--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