From: Johannes Thumshirn <johannes.thumshirn@wdc.com>
To: Zorro Lang <zlang@redhat.com>,
fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 0/5] fstests: misc fixes for zoned btrfs
Date: Fri, 28 Aug 2026 12:50:15 +0200 [thread overview]
Message-ID: <dc1d9565-277a-41aa-9683-8a8e9364a65e@wdc.com> (raw)
In-Reply-To: <apFZlAt-u7T2dTEN@zlang-mailbox>
On 8/28/26 11:54 AM, Zorro Lang wrote:
> On Fri, Aug 28, 2026 at 09:20:34AM +0200, Johannes Thumshirn wrote:
>> On 8/27/26 6:09 PM, Zorro Lang wrote:
>>> On Wed, Aug 19, 2026 at 03:16:00PM +0200, Johannes Thumshirn wrote:
>>>> Misc fixes for test failures (and a typo) when running fstests with
>>>> zoned btrfs.
>>>>
>>>> Changes to v1:
>>>> - use _require_xfs_io_command "fpunc"
>>>>
>>>> Johannes Thumshirn (5):
>>>> common/btrfs: fix awk field separator in _check_temp_fsid
>>>> btrfs/199: skip on zoned devices
>>>> generic/746: skip on zoned btrfs
>>>> btrfs/284: skip on zoned devices
>>>> generic/781: fix copyright
>>> Hi Johannes,
>>>
>>> Except for [PATCH 3/5], which still has some open points to discuss, the other
>>> 4 patches have all been acked. Given that this is a misc fixes series, would
>>> you prefer that I merge the 4 accepted patches first, or wait to take the whole
>>> series together? Either way works for me.
>>
>> Can you merge the other 4 and I'll try to get around and incorporate the
>> feedback to 3/5 ASAP and send as a standalone patch?
> Sure, you can take a look at those 4 patches in the "patches-in-queue" branch
> first.
Thanks :)
prev parent reply other threads:[~2026-08-28 10:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 13:16 [PATCH v2 0/5] fstests: misc fixes for zoned btrfs Johannes Thumshirn
2026-08-19 13:16 ` [PATCH v2 1/5] common/btrfs: fix awk field separator in _check_temp_fsid Johannes Thumshirn
2026-08-21 5:36 ` Christoph Hellwig
2026-08-19 13:16 ` [PATCH v2 2/5] btrfs/199: skip on zoned devices Johannes Thumshirn
2026-08-21 5:37 ` Christoph Hellwig
2026-08-19 13:16 ` [PATCH v2 3/5] generic/746: skip on zoned btrfs Johannes Thumshirn
2026-08-21 5:38 ` Christoph Hellwig
2026-08-24 5:41 ` Zorro Lang
2026-08-24 5:50 ` Christoph Hellwig
2026-08-19 13:16 ` [PATCH v2 4/5] btrfs/284: skip on zoned devices Johannes Thumshirn
2026-08-21 5:39 ` Christoph Hellwig
2026-08-19 13:16 ` [PATCH v2 5/5] generic/781: fix copyright Johannes Thumshirn
2026-08-27 15:58 ` Zorro Lang
2026-08-27 16:09 ` [PATCH v2 0/5] fstests: misc fixes for zoned btrfs Zorro Lang
2026-08-28 7:20 ` Johannes Thumshirn
2026-08-28 9:54 ` Zorro Lang
2026-08-28 10:50 ` Johannes Thumshirn [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=dc1d9565-277a-41aa-9683-8a8e9364a65e@wdc.com \
--to=johannes.thumshirn@wdc.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox