From: Damien Le Moal <dlemoal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
johannes.thumshirn@wdc.com, Jens Axboe <axboe@kernel.dk>
Subject: Re: Patch "block: fix cached zone reports on devices with native zone append" has been added to the 6.18-stable tree
Date: Mon, 15 Dec 2025 10:37:46 +0900 [thread overview]
Message-ID: <fd96d5f4-4e64-4c27-ace0-a12dc5111c7b@kernel.org> (raw)
In-Reply-To: <aT9lJjG3Lhz-Z3jq@laps>
On 12/15/25 10:32, Sasha Levin wrote:
> On Mon, Dec 15, 2025 at 10:20:44AM +0900, Damien Le Moal wrote:
>> On 12/15/25 09:37, Sasha Levin wrote:
>>> This is a note to let you know that I've just added the patch titled
>>>
>>> block: fix cached zone reports on devices with native zone append
>>>
>>> to the 6.18-stable tree which can be found at:
>>> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>>>
>>> The filename of the patch is:
>>> block-fix-cached-zone-reports-on-devices-with-native.patch
>>> and it can be found in the queue-6.18 subdirectory.
>>>
>>> If you, or anyone else, feels it should not be added to the stable tree,
>>> please let <stable@vger.kernel.org> know about it.
>>
>> Sasha,
>>
>> This is a fix for a new feature that was queued for and is now added to 6.19. So
>> backporting this to stable and LTS kernels is not advisable.
>
> I can drop it. It was picked up because the Fixes tag pointed to an older commit:
>
> Fixes: a6aa36e957a1 ("block: Remove zone write plugs when handling native zone append writes")
Understood. This backport will not cause any issue even if you keep it. But it
is not necessary either.
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2025-12-15 1:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251215003707.2750979-1-sashal@kernel.org>
2025-12-15 1:20 ` Patch "block: fix cached zone reports on devices with native zone append" has been added to the 6.18-stable tree Damien Le Moal
2025-12-15 1:32 ` Sasha Levin
2025-12-15 1:37 ` Damien Le Moal [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=fd96d5f4-4e64-4c27-ace0-a12dc5111c7b@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=johannes.thumshirn@wdc.com \
--cc=sashal@kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@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 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.