Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: axboe@fb.com (Jens Axboe)
Subject: [PATCH] nvme: Stop probing a removed device
Date: Wed, 12 Oct 2016 09:40:16 -0600	[thread overview]
Message-ID: <f0b0c3ae-0958-0f61-21da-90b7294cd705@fb.com> (raw)
In-Reply-To: <20161012154818.GD12429@localhost.localdomain>

On 10/12/2016 09:48 AM, Keith Busch wrote:
> On Wed, Oct 12, 2016@09:26:31AM -0600, Jens Axboe wrote:
>> On 10/12/2016 09:16 AM, Keith Busch wrote:
>>> IO queue deltion fix:
>>>
>>>   https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.infradead.org_pipermail_linux-2Dnvme_2016-2DOctober_006549.html&d=DQIBAg&c=5VD0RTtNlTh3ycd41b3MUw&r=cK1a7KivzZRh1fKQMjSm2A&m=USHj4BTLL7XH6RKDrQcfVaoEtYrs9X7WlWp86a7V7T4&s=g1WSuwsvtlK6IgJlP3yBlW4tiSJXSRgm_rgADvHVYVA&e=
>>
>> Hand applied (last hunk reject).
>>
>>> Double reset fix:
>>>
>>>   https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.infradead.org_pipermail_linux-2Dnvme_2016-2DOctober_006524.html&d=DQIBAg&c=5VD0RTtNlTh3ycd41b3MUw&r=cK1a7KivzZRh1fKQMjSm2A&m=USHj4BTLL7XH6RKDrQcfVaoEtYrs9X7WlWp86a7V7T4&s=Fv5eRNi1aBBJhmPHkNJhteHMxe_yylooeBA5-uJEkQs&e=
>>
>> Applied 1/2 - you mentioned a v2 of 2/2, and it doesn't apply since it
>> actually conflicts with the very patch referenced above.
>
> Sorry, I make this more difficult than it should be, but you have the
> intended result. The "IO queue deletion" link was the final revision of
> 2/2, but sent separately since not related or dependent on 1/2.

I thought so, thanks for confirming.

-- 
Jens Axboe

      reply	other threads:[~2016-10-12 15:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-11 17:31 [PATCH] nvme: Stop probing a removed device Keith Busch
2016-10-12 14:40 ` Jens Axboe
2016-10-12 15:16   ` Keith Busch
2016-10-12 15:26     ` Jens Axboe
2016-10-12 15:48       ` Keith Busch
2016-10-12 15:40         ` 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=f0b0c3ae-0958-0f61-21da-90b7294cd705@fb.com \
    --to=axboe@fb.com \
    /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