From: jsmart2021@gmail.com (James Smart)
Subject: [PATCH v2 0/2] nvme_fc: add uevent to allow dynamic connects
Date: Tue, 23 May 2017 09:02:41 -0700 [thread overview]
Message-ID: <bd02e8e3-a505-e3fd-be93-c817cc345453@gmail.com> (raw)
In-Reply-To: <20170523071744.GA31698@infradead.org>
On 5/23/2017 12:17 AM, Christoph Hellwig wrote:
> On Sat, May 13, 2017@12:05:57PM -0700, James Smart wrote:
>> These patches add support for generating a uevent which can be
>> caugth and converted to a nvme-cli connect-all request for the
>> FC initiator and target ports.
>
> Can you post the nvme-cli side as well so that it can be reviewed
> together?
See the patch description in Patch 2. It has the udev event rule, which
invokes nvme cli, that was used to test with.
-- james
prev parent reply other threads:[~2017-05-23 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 19:05 [PATCH v2 0/2] nvme_fc: add uevent to allow dynamic connects James Smart
2017-05-13 19:05 ` [PATCH v2 1/2] nvme_fc: create fc class and transport device James Smart
2017-05-30 8:36 ` Christoph Hellwig
2017-05-13 19:05 ` [PATCH v2 2/2] nvme_fc: add uevent for auto-connect James Smart
2017-05-30 8:39 ` Christoph Hellwig
2017-05-22 23:56 ` [PATCH v2 0/2] nvme_fc: add uevent to allow dynamic connects James Smart
2017-05-23 7:17 ` Christoph Hellwig
2017-05-23 16:02 ` James Smart [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=bd02e8e3-a505-e3fd-be93-c817cc345453@gmail.com \
--to=jsmart2021@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;
as well as URLs for NNTP newsgroup(s).