public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Keith Busch <kbusch@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
	August Wikerfors <git@augustwikerfors.se>,
	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: Tue, 1 Aug 2023 15:34:57 -0500	[thread overview]
Message-ID: <b2e741b3-b581-40fe-2c28-e4660f52003d@amd.com> (raw)
In-Reply-To: <ZMlrGNw5OMW3yxId@kbusch-mbp.dhcp.thefacebook.com>

On 8/1/2023 15:29, Keith Busch wrote:
> On Tue, Aug 01, 2023 at 06:30:52AM -0500, Mario Limonciello wrote:
>>
>> Do you want that re-sent?  Or can you just pick up from that lore link?
> 
> I got it, and applied to nvme-6.5 now.

Thanks!

If you can still change it before sending out can you add a stable tag 
as well?


  reply	other threads:[~2023-08-01 20:35 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 [this message]
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
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=b2e741b3-b581-40fe-2c28-e4660f52003d@amd.com \
    --to=mario.limonciello@amd.com \
    --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=nilskruse97@gmail.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