All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Carlos Maiolino <cem@kernel.org>
Cc: 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 07:47:32 +0200	[thread overview]
Message-ID: <20260330054732.GA5079@lst.de> (raw)
In-Reply-To: <20260330054111.3855818-5-hch@lst.de>

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.


  reply	other threads:[~2026-03-30  5:47 UTC|newest]

Thread overview: 17+ 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-31  7:12   ` Hans Holmberg
2026-03-31  9:21   ` Damien Le Moal
2026-03-30  5:40 ` [PATCH 2/4] xfs: handle too many open zones when mounting Christoph Hellwig
2026-03-31  7:34   ` Hans Holmberg
2026-03-31  9:30   ` Damien Le Moal
2026-03-30  5:40 ` [PATCH 3/4] xfs: expose the number of open zones in sysfs Christoph Hellwig
2026-03-31  7:39   ` Hans Holmberg
2026-03-31  9:35   ` Damien Le Moal
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 [this message]
2026-03-30  9:55     ` Niklas Cassel
2026-03-30 13:10       ` Christoph Hellwig
2026-03-30 13:23     ` Carlos Maiolino
2026-03-31  7:41   ` Hans Holmberg
2026-03-31  9:36   ` Damien Le Moal

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=20260330054732.GA5079@lst.de \
    --to=hch@lst.de \
    --cc=cem@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=hans.holmberg@wdc.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.