From: hch <hch@lst.de>
To: Anand Jain <anajain.sg@gmail.com>
Cc: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
Zorro Lang <zlang@redhat.com>, hch <hch@lst.de>,
Naohiro Aota <Naohiro.Aota@wdc.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Hans Holmberg <Hans.Holmberg@wdc.com>,
"fstests@vger.kernel.org" <fstests@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
Carlos Maiolino <cem@kernel.org>,
"Darrick J . Wong" <djwong@kernel.org>,
Carlos Maiolino <cmaiolino@redhat.com>
Subject: Re: [PATCH v3 3/3] generic: basic smoke for filesystems on zoned block devices
Date: Tue, 14 Oct 2025 06:30:00 +0200 [thread overview]
Message-ID: <20251014043000.GA30741@lst.de> (raw)
In-Reply-To: <97aece25-d146-4447-9756-f537acadace1@gmail.com>
On Mon, Oct 13, 2025 at 10:42:03PM +0800, Anand Jain wrote:
>> So I /think/ you just validated that the skip if !CONFIG_BLK_DEV_ZONED
>> && !CONFIG_XFS_RT check works.
>>
>
> Ah, thanks for clarifying. Any idea if the redirect to seqres.full can be
> fixed? It was missing the mkfs errors.
With "fixed" you mean not having the mkfs errors in $seqres.full? It's
kinda useful to have the messages there to see why the test wasn't run.
What speaks against having the messages logged?
next prev parent reply other threads:[~2025-10-14 4:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 8:07 [PATCH v3 0/3] fstests: basic smoke test on zoned loop device Johannes Thumshirn
2025-10-13 8:07 ` [PATCH v3 1/3] common/zoned: add _require_zloop Johannes Thumshirn
2025-10-13 8:43 ` Naohiro Aota
2025-10-14 4:33 ` Christoph Hellwig
2025-10-13 8:07 ` [PATCH v3 2/3] common/zoned: add _create_zloop Johannes Thumshirn
2025-10-14 9:04 ` Naohiro Aota
2025-10-13 8:07 ` [PATCH v3 3/3] generic: basic smoke for filesystems on zoned block devices Johannes Thumshirn
2025-10-13 13:55 ` Anand Jain
2025-10-13 14:06 ` Johannes Thumshirn
2025-10-13 14:42 ` Anand Jain
2025-10-14 4:30 ` hch [this message]
2025-10-14 14:38 ` Anand Jain
2025-10-15 4:09 ` hch
2025-10-14 4:33 ` 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=20251014043000.GA30741@lst.de \
--to=hch@lst.de \
--cc=Hans.Holmberg@wdc.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=anajain.sg@gmail.com \
--cc=cem@kernel.org \
--cc=cmaiolino@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--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 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.