Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: jsmart2021@gmail.com (James Smart)
Subject: [PATCH v2 0/2] nvme_fc: add uevent to allow dynamic connects
Date: Mon, 22 May 2017 16:56:54 -0700	[thread overview]
Message-ID: <95e4df93-46d8-55b2-a64f-afbf7f730769@gmail.com> (raw)
In-Reply-To: <20170513190559.25484-1-jsmart2021@gmail.com>

On 5/13/2017 12:05 PM, 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.
>
> The patches were cut on nvme-4.12 after apply the patches contained in
> http://lists.infradead.org/pipermail/linux-nvme/2017-May/010156.html
>
> James Smart (2):
>   nvme_fc: create fc class and transport device
>   nvme_fc: add uevent for auto-connect
>
>  drivers/nvme/host/fc.c         | 102 +++++++++++++++++++++++++++++++++++++++--
>  include/linux/nvme-fc-driver.h |   2 +
>  2 files changed, 100 insertions(+), 4 deletions(-)
>


Any comments on this series ?

-- james

  parent reply	other threads:[~2017-05-22 23:56 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 ` James Smart [this message]
2017-05-23  7:17 ` [PATCH v2 0/2] nvme_fc: add uevent to allow dynamic connects Christoph Hellwig
2017-05-23 16:02   ` James Smart

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=95e4df93-46d8-55b2-a64f-afbf7f730769@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