From: jsmart2021@gmail.com (James Smart)
Subject: [PATCH] nvme core: allow controller RESETTING to RECONNECTING transition
Date: Thu, 4 May 2017 08:07:11 -0700 [thread overview]
Message-ID: <dc09239d-962f-a48b-692b-375f65757489@gmail.com> (raw)
In-Reply-To: <a531ab03-f3d8-355c-80ec-9f66437ae67e@grimberg.me>
On 5/3/2017 9:55 AM, Sagi Grimberg wrote:
> This sort of discussion really calls for a unification of control and
> the error handling flows for all transports, with a single state
> machine semantics. I'm currently looking into it, but I suspect it'll
> take me a little while...
I don't think it has to be that drastic, but at least a common
understanding of what the states mean/span should be known.
-- james
prev parent reply other threads:[~2017-05-04 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 18:54 [PATCH] nvme core: allow controller RESETTING to RECONNECTING transition jsmart2021
2017-05-03 7:59 ` Sagi Grimberg
2017-05-03 15:32 ` James Smart
2017-05-03 16:55 ` Sagi Grimberg
2017-05-04 15:07 ` James Smart [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=dc09239d-962f-a48b-692b-375f65757489@gmail.com \
--to=jsmart2021@gmail.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