From: jsmart2021@gmail.com (James Smart)
Subject: [PATCH v3 0/3] nvme_fc: add uevent to allow dynamic connects
Date: Thu, 14 Sep 2017 10:38:40 -0700 [thread overview]
Message-ID: <20170914173843.3195-1-jsmart2021@gmail.com> (raw)
These patches add support for generating a uevent which can be
caught and converted to a nvme-cli connect-all request for the
FC initiator and target ports.
Also contains a patch to catch connection attempts that duplicate
already-in-existence associations.
Cut on nvme-4.14
James Smart (3):
nvme_fc: create fc class and transport device
nvme_fc: add uevent for auto-connect
nvme_fc: Avoid duplicate associations between same port pairs
drivers/nvme/host/fc.c | 132 ++++++++++++++++++++++++++++++++++++++++-
include/linux/nvme-fc-driver.h | 2 +
2 files changed, 133 insertions(+), 1 deletion(-)
--
2.13.1
next reply other threads:[~2017-09-14 17:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 17:38 James Smart [this message]
2017-09-14 17:38 ` [PATCH v3 1/3] nvme_fc: create fc class and transport device James Smart
2017-09-18 16:13 ` Christoph Hellwig
2017-09-20 10:30 ` Johannes Thumshirn
2017-09-20 17:50 ` Christoph Hellwig
2017-09-21 5:16 ` Johannes Thumshirn
2017-09-14 17:38 ` [PATCH v3 2/3] nvme_fc: add uevent for auto-connect James Smart
2017-09-18 16:14 ` Christoph Hellwig
2017-09-19 14:53 ` James Smart
2017-09-20 17:50 ` Christoph Hellwig
2017-09-14 17:38 ` [PATCH v3 3/3] nvme_fc: Avoid duplicate associations between same port pairs James Smart
2017-09-18 16:12 ` Christoph Hellwig
2017-09-18 16:28 ` James Smart
2017-09-18 23:17 ` Christoph Hellwig
2017-09-19 0:07 ` James Smart
2017-09-20 11:09 ` Sagi Grimberg
2017-10-04 7:48 ` [PATCH v3 0/3] nvme_fc: add uevent to allow dynamic connects Christoph Hellwig
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=20170914173843.3195-1-jsmart2021@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