From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH 1/3] nvme: separate out nvme_ctrl_state_name()
Date: Fri, 17 May 2019 16:59:05 +0900 [thread overview]
Message-ID: <20190517075904.GA26359@minwooim-desktop> (raw)
In-Reply-To: <20190517064254.95561-2-hare@suse.de>
Hi Hannes,
Thanks for applying my review point on this.
This looks good to me.
Reviewed-by: Minwoo Im <minwoo.im.dev at gmail.com>
next prev parent reply other threads:[~2019-05-17 7:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2019-05-17 6:42 ` [PATCH 2/3] nvme-fc: track state change failures during reconnect Hannes Reinecke
2019-05-17 6:42 ` [PATCH 3/3] nvme-fc: fail reconnect if state change fails Hannes Reinecke
2019-05-17 16:10 ` James Smart
2019-05-17 18:34 ` Hannes Reinecke
2019-05-17 18:52 ` James Smart
-- strict thread matches above, loose matches on Subject: below --
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
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=20190517075904.GA26359@minwooim-desktop \
--to=minwoo.im.dev@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