From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH nvme-cli] fabrics: add option to supply keep-alive-timeout for connect-all
Date: Wed, 25 Apr 2018 11:56:29 -0600 [thread overview]
Message-ID: <20180425175629.GA454@localhost.localdomain> (raw)
In-Reply-To: <20180425174923.9387-1-jthumshirn@suse.de>
On Wed, Apr 25, 2018@11:49:23AM -0600, Johannes Thumshirn wrote:
> Currently we can't supply a keep-alive-timeout when doing a nvme
> connect-all, but we can supply it when doing nvme connect.
>
> Bring connect-all in line with connect.
>
> Signed-off-by: Johannes Thumshirn <jthumshirn at suse.de>
Applied, thanks!
prev parent reply other threads:[~2018-04-25 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 17:49 [PATCH nvme-cli] fabrics: add option to supply keep-alive-timeout for connect-all Johannes Thumshirn
2018-04-25 17:56 ` Keith Busch [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=20180425175629.GA454@localhost.localdomain \
--to=keith.busch@intel.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