All of lore.kernel.org
 help / color / mirror / Atom feed
From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: [PATCH 5/7 v2] nvme-fabrics: Add host FC transport support
Date: Wed, 12 Oct 2016 10:43:43 -0700	[thread overview]
Message-ID: <1476294223.5410.74.camel@linux.intel.com> (raw)
In-Reply-To: <20161012092411.GF12972@infradead.org>

On Wed, 2016-10-12@02:24 -0700, Christoph Hellwig wrote:
> > 
> > +	??To configure a NVMe over Fabrics controller use the
> > nvme-cli tool
> > +	??from https://github.com/linux-nvme/nvme-cli.
> 
> Talking about nvme-cli, can you post the FC support patches for that
> as well?

Yes, this would be good, esp since Christoph and I have been writing
man pages and mention "fc" in one of the parameters.

(In fact, providing an fc example in the man pages would go a long way
to enabling fc people using nvme-cli).

I'll try and give your series a look after this patchset is resubmitted
with Christoph's feedback.

J

  reply	other threads:[~2016-10-12 17:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 23:09 [PATCH 5/7 v2] nvme-fabrics: Add host FC transport support James Smart
2016-10-12  9:24 ` Christoph Hellwig
2016-10-12 17:43   ` J Freyensee [this message]
2016-10-12 19:54   ` James Smart
2016-10-13  9:51     ` 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=1476294223.5410.74.camel@linux.intel.com \
    --to=james_p_freyensee@linux.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.