From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 2/2] nvme: no need to wait for the reset when keepalive fails
Date: Thu, 15 Jun 2017 15:15:18 +0200 [thread overview]
Message-ID: <20170615131518.GA23908@lst.de> (raw)
In-Reply-To: <1f0dd933-1535-c22e-d44b-665a2df12ee4@grimberg.me>
On Thu, Jun 15, 2017@04:04:42PM +0300, Sagi Grimberg wrote:
>> I dropped the admin_queue checks as request by you.
>
> Then I don't see it. is it under the same title?
I was sent in the same series as the patch you reviewed, thus the
2/2 in the subject.
next prev parent reply other threads:[~2017-06-15 13:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 16:27 [PATCH 1/2] nvme: move reset workqueue handling to common code Christoph Hellwig
2017-06-12 16:27 ` [PATCH 2/2] nvme: no need to wait for the reset when keepalive fails Christoph Hellwig
2017-06-15 8:52 ` Sagi Grimberg
2017-06-15 12:16 ` Christoph Hellwig
2017-06-15 12:46 ` Sagi Grimberg
2017-06-15 12:46 ` Christoph Hellwig
2017-06-15 13:04 ` Sagi Grimberg
2017-06-15 13:15 ` Christoph Hellwig [this message]
2017-06-15 13:20 ` Sagi Grimberg
-- strict thread matches above, loose matches on Subject: below --
2017-06-15 13:42 nvme reset factor, v3 Christoph Hellwig
2017-06-15 13:42 ` [PATCH 2/2] nvme: no need to wait for the reset when keepalive fails Christoph Hellwig
2017-06-15 16:23 ` Max Gurtovoy
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=20170615131518.GA23908@lst.de \
--to=hch@lst.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.