From: axboe@kernel.dk (Jens Axboe)
Subject: [PATCH v2] nvme: Suspend all queues before deletion
Date: Thu, 11 Aug 2016 09:34:41 -0600 [thread overview]
Message-ID: <ff47dd4c-b55a-b5a0-53db-a290d87a537c@kernel.dk> (raw)
In-Reply-To: <87oa4zpivj.fsf@linux.vnet.ibm.com>
On 08/11/2016 06:53 AM, Gabriel Krisman Bertazi wrote:
> Keith Busch <keith.busch at intel.com> writes:
>
>> On Tue, Aug 02, 2016@11:10:38PM -0300, Gabriel Krisman Bertazi wrote:
>>> Yes, that approach seems to be ok. Please take the tested v2 below, in
>>> which I apply your suggestion, as well as clean up a bit the code in
>>> nvme_disable_io_queues and simplify the logic a bit.
>>
>> The new patch looks good to me.
>
> Hi, any chance we can get this in for 4.8-rc2 or 4.8-rc3? It fixes
> important bugs for us.
I'll queue it up for 4.8.
--
Jens Axboe
prev parent reply other threads:[~2016-08-11 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 17:15 [PATCH] nvme: Suspend all queues before deletion Gabriel Krisman Bertazi
2016-08-02 22:23 ` Keith Busch
2016-08-03 2:10 ` [PATCH v2] " Gabriel Krisman Bertazi
2016-08-04 21:07 ` Keith Busch
2016-08-11 12:53 ` Gabriel Krisman Bertazi
2016-08-11 15:34 ` Jens Axboe [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=ff47dd4c-b55a-b5a0-53db-a290d87a537c@kernel.dk \
--to=axboe@kernel.dk \
/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;
as well as URLs for NNTP newsgroup(s).