From: sashal@kernel.org (Sasha Levin)
Subject: [PATCH AUTOSEL 4.19 59/64] nvme-pci: fix rapid add remove sequence
Date: Mon, 11 Mar 2019 13:21:44 -0400 [thread overview]
Message-ID: <20190311172144.GF158926@sasha-vm> (raw)
In-Reply-To: <20190228151642.GA21796@localhost.localdomain>
On Thu, Feb 28, 2019@08:16:43AM -0700, Keith Busch wrote:
>On Thu, Feb 28, 2019@10:11:00AM -0500, Sasha Levin wrote:
>> From: Keith Busch <keith.busch at intel.com>
>>
>> [ Upstream commit 5c959d73dba6495ec01d04c206ee679d61ccb2b0 ]
>
>This patch was broken, so please make sure to include the one that
>fixes this:
>
> Upstream commit 4726bcf30fad37cc555cd9dcd6c73f2b2668c879
> ("nvme-pci: add missing unlock for reset error")
I've queued this one as well, thank you.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-03-11 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190228151105.11277-1-sashal@kernel.org>
2019-02-28 15:10 ` [PATCH AUTOSEL 4.19 58/64] nvme: lock NS list changes while handling command effects Sasha Levin
2019-02-28 15:11 ` [PATCH AUTOSEL 4.19 59/64] nvme-pci: fix rapid add remove sequence Sasha Levin
2019-02-28 15:16 ` Keith Busch
2019-03-11 17:21 ` Sasha Levin [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=20190311172144.GF158926@sasha-vm \
--to=sashal@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