From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] nvme-cli: add duplicate_connect parameter support
Date: Tue, 17 Oct 2017 08:39:01 -0600 [thread overview]
Message-ID: <20171017143900.GA32530@localhost.localdomain> (raw)
In-Reply-To: <20171011003536.5996-1-jsmart2021@gmail.com>
On Tue, Oct 10, 2017@05:35:36PM -0700, James Smart wrote:
> Add support for the duplicate_connect parameter for the fabrics
> device.
>
> Rather than add yet another 6-line code block, created a small helper
> routine invoked for each argument option.
>
> Signed-off-by: James Smart <james.smart at broadcom.com>
Thanks, applied.
prev parent reply other threads:[~2017-10-17 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 0:35 [PATCH] nvme-cli: add duplicate_connect parameter support James Smart
2017-10-17 14:39 ` 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=20171017143900.GA32530@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.