From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
zlang@kernel.org, dlemoal@kernel.org, hans.holmberg@wdc.com,
fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v3] xfs: add a test for number of open zones on conventional devices
Date: Wed, 15 Apr 2026 07:22:39 +0200 [thread overview]
Message-ID: <20260415052239.GA26559@lst.de> (raw)
In-Reply-To: <20260414185914.GB150005@frogsfrogsfrogs>
On Tue, Apr 14, 2026 at 11:59:14AM -0700, Darrick J. Wong wrote:
> > +_require_scratch_nocheck
> > +_require_odirect
> > +_require_non_zoned_device $SCRATCH_DEV
> > +_require_non_zoned_device $SCRATCH_RTDEV
>
> Seems fine to me still, though I wonder if you still need to check
> SCRATCH_RTDEV if you're opencoding the mkfs/mount calls?
This can be dropped now, thanks!
next prev parent reply other threads:[~2026-04-15 5:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 7:55 [PATCH v3] xfs: add a test for number of open zones on conventional devices Christoph Hellwig
2026-04-14 18:59 ` Darrick J. Wong
2026-04-15 5:22 ` Christoph Hellwig [this message]
2026-04-16 16:54 ` Zorro Lang
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=20260415052239.GA26559@lst.de \
--to=hch@lst.de \
--cc=djwong@kernel.org \
--cc=dlemoal@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hans.holmberg@wdc.com \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@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