public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
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


  parent reply	other threads:[~2023-08-12  5:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31 18:51 [PATCH] nvme: Don't fail to resume if NSIDs change Mario Limonciello
2023-07-31 19:10 ` Keith Busch
2023-07-31 19:41   ` Christoph Hellwig
2023-07-31 19:54   ` August Wikerfors
2023-07-31 20:09     ` Limonciello, Mario
2023-07-31 20:10       ` Christoph Hellwig
2023-07-31 20:14         ` Limonciello, Mario
2023-08-01 11:24           ` Christoph Hellwig
2023-08-01 11:30             ` Mario Limonciello
2023-08-01 20:29               ` Keith Busch
2023-08-01 20:34                 ` Mario Limonciello
2023-08-11 20:19                   ` 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]
2023-07-31 19:11 ` August Wikerfors

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