From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH v2] nvme_fc: retry initial controller connections 3 times
Date: Mon, 16 Oct 2017 05:50:40 -0700 [thread overview]
Message-ID: <20171016125040.GE26833@infradead.org> (raw)
In-Reply-To: <20171009233922.7216-1-jsmart2021@gmail.com>
Thanks,
I will apply this to the nvme-4.14 tree.
prev parent reply other threads:[~2017-10-16 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 23:39 [PATCH v2] nvme_fc: retry initial controller connections 3 times James Smart
2017-10-11 11:09 ` Sagi Grimberg
2017-10-11 15:07 ` James Smart
2017-10-16 12:50 ` Christoph Hellwig [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=20171016125040.GE26833@infradead.org \
--to=hch@infradead.org \
/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).