From: Greg KH <gregkh@linuxfoundation.org>
To: August Wikerfors <git@augustwikerfors.se>
Cc: stable@vger.kernel.org,
Mario Limonciello <mario.limonciello@amd.com>,
Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
axboe@fb.com, sagi@grimberg.me, linux-nvme@lists.infradead.org,
linux-kernel@vger.kernel.org, nilskruse97@gmail.com,
David.Chang@amd.com
Subject: Re: [PATCH] nvme: Don't fail to resume if NSIDs change
Date: Sat, 12 Aug 2023 07:57:11 +0200 [thread overview]
Message-ID: <2023081258-marital-idly-e4da@gregkh> (raw)
In-Reply-To: <0f422dbe-2e3f-4401-be87-2963cbbc1234@augustwikerfors.se>
On Fri, Aug 11, 2023 at 10:19:35PM +0200, August Wikerfors wrote:
> On 2023-08-01 22:34, Mario Limonciello wrote:
> > If you can still change it before sending out can you add a stable tag
> > as well?
>
> This didn't get added in time, so, stable team, please backport:
>
> 688b419c57c1 ("nvme-pci: add NVME_QUIRK_BOGUS_NID for Samsung PM9B1 256G and 512G")
Now queued up to 6.4.y and 6.1.y, thanks.
greg k-h
prev parent reply other threads:[~2023-08-12 5:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230731185103.18436-1-mario.limonciello@amd.com>
[not found] ` <ZMgHE2wu4T4OfrTR@kbusch-mbp>
[not found] ` <040c5788-1a7b-26ea-23cc-ba239c76efa9@augustwikerfors.se>
[not found] ` <39697f68-9dc8-7692-7210-b75cce32c6ce@amd.com>
[not found] ` <20230731201047.GA14034@lst.de>
[not found] ` <36319a0f-34a6-9353-bc52-4d4d0fac27a5@amd.com>
[not found] ` <20230801112403.GA3972@lst.de>
[not found] ` <ae7fb9b2-d692-f9b8-5130-4555cc489846@amd.com>
[not found] ` <ZMlrGNw5OMW3yxId@kbusch-mbp.dhcp.thefacebook.com>
[not found] ` <b2e741b3-b581-40fe-2c28-e4660f52003d@amd.com>
2023-08-11 20:19 ` [PATCH] nvme: Don't fail to resume if NSIDs change August Wikerfors
2023-08-11 20:59 ` Keith Busch
2023-08-12 5:57 ` Greg KH
2023-08-12 5:57 ` Greg KH [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=2023081258-marital-idly-e4da@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=David.Chang@amd.com \
--cc=axboe@fb.com \
--cc=git@augustwikerfors.se \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mario.limonciello@amd.com \
--cc=nilskruse97@gmail.com \
--cc=sagi@grimberg.me \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox