From: Mark Brown <broonie@kernel.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: Tao Cui <cui.tao@linux.dev>,
linux-next@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, cuitao@kylinos.cn
Subject: Re: next-20260917 and next-20260918: merge of the block tree breaks all zoned devices
Date: Mon, 21 Sep 2026 12:29:13 +0200 [thread overview]
Message-ID: <arEG-YH7Q7ansx6o@sirena.co.uk> (raw)
In-Reply-To: <0ed54aa9-2cc6-4051-abe7-8144f39f6bed@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 216 bytes --]
On Mon, Sep 21, 2026 at 11:31:11AM +0900, Damien Le Moal wrote:
> Mark, Attaching a v2 diff for corrected the conflict resolution. This is on top
> of the current linux-next.
I've replaced the patch with this one.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-09-21 10:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 12:58 next-20260917 and next-20260918: merge of the block tree breaks all zoned devices Tao Cui
2026-09-20 13:12 ` Stephen Rothwell
2026-09-20 15:18 ` Mark Brown
2026-09-20 22:37 ` Damien Le Moal
2026-09-21 0:49 ` Tao Cui
2026-09-21 2:07 ` Damien Le Moal
2026-09-21 2:31 ` Damien Le Moal
2026-09-21 10:29 ` Mark Brown [this message]
2026-09-21 8:24 ` Mark Brown
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=arEG-YH7Q7ansx6o@sirena.co.uk \
--to=broonie@kernel.org \
--cc=axboe@kernel.dk \
--cc=cui.tao@linux.dev \
--cc=cuitao@kylinos.cn \
--cc=dlemoal@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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