linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: Zorro Lang <zlang@redhat.com>, Christoph Hellwig <hch@lst.de>,
	Naohiro Aota <naohiro.aota@wdc.com>,
	linux-btrfs@vger.kernel.org,
	Hans Holmberg <hans.holmberg@wdc.com>,
	fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 0/2] fstests: basic smoke test on zoned loop device
Date: Tue, 7 Oct 2025 06:15:39 +0200	[thread overview]
Message-ID: <20251007041539.GA15817@lst.de> (raw)
In-Reply-To: <20251006132455.140149-1-johannes.thumshirn@wdc.com>

On Mon, Oct 06, 2025 at 03:24:53PM +0200, Johannes Thumshirn wrote:
> Add a very basic smoke test on a zoned loopback device to check that noone is
> accidentially breaking support for zoned block devices in filesystems that
> support these.

Thanks!  Having a least minimal zoned file system coverage in standard
xfstests runs seems really useful.


      parent reply	other threads:[~2025-10-07  4:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-06 13:24 [PATCH 0/2] fstests: basic smoke test on zoned loop device Johannes Thumshirn
2025-10-06 13:24 ` [PATCH 1/2] common/zoned: add _require_zloop Johannes Thumshirn
2025-10-06 18:06   ` Carlos Maiolino
2025-10-07  4:13   ` Christoph Hellwig
2025-10-06 13:24 ` [PATCH] generic: basic smoke for filesystems on zoned block devices Johannes Thumshirn
2025-10-06 18:40   ` Carlos Maiolino
2025-10-07  6:20     ` Johannes Thumshirn
2025-10-07  7:54       ` Carlos Maiolino
2025-10-07  4:15   ` Christoph Hellwig
2025-10-17 14:57   ` Zorro Lang
2025-10-17 18:21     ` Zorro Lang
2025-10-07  4:15 ` 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=20251007041539.GA15817@lst.de \
    --to=hch@lst.de \
    --cc=fstests@vger.kernel.org \
    --cc=hans.holmberg@wdc.com \
    --cc=johannes.thumshirn@wdc.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=naohiro.aota@wdc.com \
    --cc=zlang@redhat.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;
as well as URLs for NNTP newsgroup(s).