From: hare@suse.de (Hannes Reinecke)
Subject: [PATCH 2/7] nvme_fc: remove setting DNR on exception conditions
Date: Tue, 8 May 2018 07:58:17 +0200 [thread overview]
Message-ID: <20180508075817.1195bd13@pentland.suse.de> (raw)
In-Reply-To: <20180508001214.8951-3-jsmart2021@gmail.com>
On Mon, 7 May 2018 17:12:09 -0700
"James Smart" <jsmart2021@gmail.com> wrote:
> Current code will set DNR if the controller is deleting or there is
> an error during controller init. None of this is necessary.
>
> remove the code that sets DNR
>
> Signed-off-by: James Smart <james.smart at broadcom.com>
> ---
> drivers/nvme/host/fc.c | 10 ----------
> 1 file changed, 10 deletions(-)
>
Reviewed-by: Hannes Reinecke <hare at suse.com>
Cheers,
Hannes
next prev parent reply other threads:[~2018-05-08 5:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 0:12 [PATCH 0/7] nvme_fc: asynchronous controller create and simple discovery James Smart
2018-05-08 0:12 ` [PATCH 1/7] nvme: remove unnecessary controller subnqn validation James Smart
2018-05-08 5:57 ` Hannes Reinecke
2018-05-08 0:12 ` [PATCH 2/7] nvme_fc: remove setting DNR on exception conditions James Smart
2018-05-08 5:58 ` Hannes Reinecke [this message]
2018-05-08 0:12 ` [PATCH 3/7] nvme_fc: retry failures to set io queue count James Smart
2018-05-08 6:00 ` Hannes Reinecke
2018-05-11 20:19 ` James Smart
2018-05-08 0:12 ` [PATCH 4/7] nvme_fc: remove reinit_request routine James Smart
2018-05-08 6:01 ` Hannes Reinecke
2018-05-08 0:12 ` [PATCH 5/7] nvme_fc: change controllers first connect to use reconnect path James Smart
2018-05-08 6:03 ` Hannes Reinecke
2018-05-08 0:12 ` [PATCH 6/7] nvme_fc: fix nulling of queue data on reconnect James Smart
2018-05-08 6:05 ` Hannes Reinecke
2018-05-08 15:12 ` James Smart
2018-05-08 15:28 ` Hannes Reinecke
2018-05-08 0:12 ` [PATCH 7/7] nvme_fc: add 'nvme_discovery' sysfs attribute to fc transport device James Smart
2018-05-08 6:06 ` Hannes Reinecke
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=20180508075817.1195bd13@pentland.suse.de \
--to=hare@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).