From: james.smart@broadcom.com (James Smart)
Subject: [PATCH 1/3] nvme: separate out nvme_ctrl_state_name()
Date: Thu, 16 May 2019 09:24:07 -0700 [thread overview]
Message-ID: <69728e55-cbc0-6e2a-730b-51bc2e5b7726@broadcom.com> (raw)
In-Reply-To: <20190516083740.95894-2-hare@suse.de>
On 5/16/2019 1:37 AM, Hannes Reinecke wrote:
> Separate out nvme_ctrl_state_name() to return the controller state
> as a string.
>
> Signed-off-by: Hannes Reinecke <hare at suse.com>
> ---
> drivers/nvme/host/core.c | 36 +++++++++++++++++++++++-------------
> drivers/nvme/host/nvme.h | 1 +
> 2 files changed, 24 insertions(+), 13 deletions(-)
>
>
Reviewed-by:? James Smart? <james.smart at broadcom.com>
next prev parent reply other threads:[~2019-05-16 16:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 8:37 [PATCH 0/3] nvme-fc: track state change failures Hannes Reinecke
2019-05-16 8:37 ` [PATCH 1/3] nvme: separate out nvme_ctrl_state_name() Hannes Reinecke
2019-05-16 13:55 ` Minwoo Im
2019-05-16 16:24 ` James Smart [this message]
2019-05-16 8:37 ` [PATCH 2/3] nvme-fc: track state change failures during reconnect Hannes Reinecke
2019-05-16 16:24 ` James Smart
2019-05-16 8:37 ` [PATCH 3/3] nvme-fc: fail reconnect if state change fails Hannes Reinecke
2019-05-16 16:25 ` James Smart
2019-05-18 0:18 ` Arun Easi
2019-05-18 0:21 ` Arun Easi
-- strict thread matches above, loose matches on Subject: below --
2019-05-17 6:42 [PATCHv2 0/3] nvme-fc: track state change failures Hannes Reinecke
2019-05-17 6:42 ` [PATCH 1/3] nvme: separate out nvme_ctrl_state_name() Hannes Reinecke
2019-05-17 7:59 ` Minwoo Im
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=69728e55-cbc0-6e2a-730b-51bc2e5b7726@broadcom.com \
--to=james.smart@broadcom.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