From: Johannes Thumshirn <johannes.thumshirn@wdc.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-btrfs@vger.kernel.org, naohiro.aota@wdc.com,
Dongjiang Zhu <zhudongjiang@fygo.io>
Subject: Re: [PATCH 1/4] btrfs: zoned: track only sequential zones as active
Date: Tue, 25 Aug 2026 11:10:30 +0200 [thread overview]
Message-ID: <8a708d2f-a835-45ce-bbde-b5b99852c179@wdc.com> (raw)
In-Reply-To: <32245f5e-59f1-4e9f-bd24-d55f2a17f158@gmx.com>
On 8/25/26 12:40 AM, Qu Wenruo wrote:
>> Looks good, two small nits though in case you need to resend the series:
>> 1) Please don't do the [CAUSE], [BUG], [FIX] thingy, I know Qu does
>> it but
>> noone else does that.
>
> Sorry, I thought that was a good way to explain a bug, but this
> doesn't look like so for everyone else.
>
> I'll also change the future style.
Nah it's kind of your signature, like me writing Byte instead of Bye.
next prev parent reply other threads:[~2026-08-25 9:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 6:49 [PATCH 0/4] btrfs: zoned: fix active-zone accounting and transitions Dongjiang Zhu
2026-08-24 6:49 ` [PATCH 1/4] btrfs: zoned: track only sequential zones as active Dongjiang Zhu
2026-08-24 13:55 ` Johannes Thumshirn
2026-08-24 22:40 ` Qu Wenruo
2026-08-25 9:10 ` Johannes Thumshirn [this message]
2026-08-25 3:01 ` Dongjiang Zhu
2026-08-24 6:49 ` [PATCH 2/4] btrfs: zoned: recover active non-data block group roles on mount Dongjiang Zhu
2026-08-24 14:42 ` Johannes Thumshirn
2026-08-25 3:08 ` Dongjiang Zhu
2026-08-25 10:02 ` Johannes Thumshirn
2026-08-24 6:49 ` [PATCH 3/4] btrfs: zoned: remove obsolete non-data block group activation helper Dongjiang Zhu
2026-08-24 15:51 ` Johannes Thumshirn
2026-08-24 6:49 ` [PATCH 4/4] btrfs: zoned: serialize zone finishing per block group Dongjiang Zhu
2026-08-24 16:00 ` Johannes Thumshirn
2026-08-25 3:16 ` Dongjiang Zhu
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=8a708d2f-a835-45ce-bbde-b5b99852c179@wdc.com \
--to=johannes.thumshirn@wdc.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=naohiro.aota@wdc.com \
--cc=quwenruo.btrfs@gmx.com \
--cc=zhudongjiang@fygo.io \
/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