From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
zlang@kernel.org, hans.holmberg@wdc.com,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] common: skip zoned devices in _require_populate_commands
Date: Mon, 12 May 2025 17:27:20 +0200 [thread overview]
Message-ID: <20250512152720.GA9517@lst.de> (raw)
In-Reply-To: <20250512150824.GD2701446@frogsfrogsfrogs>
On Mon, May 12, 2025 at 08:08:24AM -0700, Darrick J. Wong wrote:
> Do you need to _notrun the other mdrestore tests too?
All the the other ones seem to just restore to files, which works.
> I was wondering why this patch didn't add a helper:
>
> # Check if mdrestore is supported, must come after _scratch_check
> _require_scratch_mdrestore() {
That seems reasonable, I'll look into it.
prev parent reply other threads:[~2025-05-12 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 13:18 [PATCH] common: skip zoned devices in _require_populate_commands Christoph Hellwig
2025-05-12 15:08 ` Darrick J. Wong
2025-05-12 15:27 ` Christoph Hellwig [this message]
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=20250512152720.GA9517@lst.de \
--to=hch@lst.de \
--cc=djwong@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;
as well as URLs for NNTP newsgroup(s).