From: David Sterba <dsterba@suse.cz>
To: Naohiro Aota <naohiro.aota@wdc.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 0/4] btrfs-progs: tests: add new mkfs test for zoned device
Date: Thu, 16 Oct 2025 19:53:05 +0200 [thread overview]
Message-ID: <20251016175305.GI13776@twin.jikos.cz> (raw)
In-Reply-To: <20250910050412.2138579-1-naohiro.aota@wdc.com>
On Wed, Sep 10, 2025 at 02:04:08PM +0900, Naohiro Aota wrote:
> This series adds a new mkfs test for zoned device. The test is based on
> mkfs-tests/001-basic-profiles, but uses nullb devices instead of loop
> devices, to set a zoned profile.
>
> Two preparation patches are necessaly for the test case. The first and
> second one fix the error handling of _find_free_index(). And, the third
> one adds wait_for_nullbdevs like the loop device's counterpart.
>
> Changes:
> - v2
> - Refine error/warn helpers not to print the message to stdout.
> - Drop cond_wait_for_nullbdevs.
> - Check if btrfs-progs is build with EXPERIMENTAL in the test.
>
> Naohiro Aota (4):
> btrfs-progs: tests: output error/warn message to stderr
> btrfs-progs: tests: check nullb index for the error case
> btrfs-progs: tests: add wait_for_nullbdevs
> btrfs-progs: tests: add new mkfs test for zoned device
Added to devel, sorry for the delay.
prev parent reply other threads:[~2025-10-16 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 5:04 [PATCH v2 0/4] btrfs-progs: tests: add new mkfs test for zoned device Naohiro Aota
2025-09-10 5:04 ` [PATCH v2 1/4] btrfs-progs: tests: output error/warn message to stderr Naohiro Aota
2025-09-10 5:22 ` Qu Wenruo
2025-09-10 5:04 ` [PATCH v2 2/4] btrfs-progs: tests: check nullb index for the error case Naohiro Aota
2025-09-10 5:22 ` Qu Wenruo
2025-09-10 5:04 ` [PATCH v2 3/4] btrfs-progs: tests: add wait_for_nullbdevs Naohiro Aota
2025-09-10 5:22 ` Qu Wenruo
2025-09-10 5:04 ` [PATCH v2 4/4] btrfs-progs: tests: add new mkfs test for zoned device Naohiro Aota
2025-10-16 17:53 ` David Sterba [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=20251016175305.GI13776@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=naohiro.aota@wdc.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