From: Keith Busch <kbusch@kernel.org>
To: Saeed Mirzamohammadi <saeed.mirzamohammadi@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Jens Axboe <axboe@kernel.dk>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] nvme: don't apply NVME_QUIRK_DEALLOCATE_ZEROES when DSM is not supported
Date: Mon, 2 Dec 2024 11:08:21 -0700 [thread overview]
Message-ID: <Z033lXyZt4w4V6be@kbusch-mbp> (raw)
In-Reply-To: <843B01FE-5121-4BF4-A305-65F38A1C05E9@oracle.com>
On Mon, Dec 02, 2024 at 06:03:02PM +0000, Saeed Mirzamohammadi wrote:
> Thanks! Can this be applied to 6.11+ stable releases as well since the broken commit is in 6.9.y?
I don't think it can go to 6.9.y because it is not an LTS and that
branch appears to have already ended stable support.
Since this patch has the "Fixes" tag though, the stable auto patch
selection should grab it for the appropriate stable branches that are
still supported, so branches like 6.11.y and 6.6.y should get it. I'll
keep an eye out for it after the next pull request just to make sure.
prev parent reply other threads:[~2024-12-02 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241127152849epcas5p3872af708d33fbfb00fd3b703b879b273@epcas5p3.samsung.com>
2024-11-27 6:42 ` [PATCH] nvme: don't apply NVME_QUIRK_DEALLOCATE_ZEROES when DSM is not supported Christoph Hellwig
2024-11-27 7:48 ` Chaitanya Kulkarni
2024-11-27 15:20 ` Nitesh Shetty
2024-11-27 15:45 ` Keith Busch
2024-11-27 15:48 ` Christoph Hellwig
2024-11-27 15:52 ` Keith Busch
2024-12-02 17:54 ` Keith Busch
2024-12-02 18:03 ` Saeed Mirzamohammadi
2024-12-02 18:08 ` Keith Busch [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=Z033lXyZt4w4V6be@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--cc=saeed.mirzamohammadi@oracle.com \
--cc=sagi@grimberg.me \
/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