All of lore.kernel.org
 help / color / mirror / Atom feed
From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: nvme-cli: Plea for help to document fabrics commands
Date: Thu, 22 Sep 2016 11:27:48 -0700	[thread overview]
Message-ID: <1474568868.15303.22.camel@linux.intel.com> (raw)

With NVMe-over-Fabrics being merged into the existing NVMe code base,
contributions were also made to nvme-cli to enable fabrics features in
the tool. However, documentation (specifically man pages) are lacking
for fabrics features in nvme-cli, which doesn't bode well as the tool
has maintained very good documentation for all the other
commands/features that already exist for NVMe.

I would like to propose a divide-and-conquer strategy to get new man
pages added for the fabrics features to get it up to par with the rest
of the tool.

I'll volunteer to take on "discover".

I believe that leaves "connect-all", "connect", and "disconnect" still
to be documented (unless I missed something...Christoph or Ming) for
other people to conquer?

Thanks,
Jay

             reply	other threads:[~2016-09-22 18:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22 18:27 J Freyensee [this message]
2016-09-23  3:28 ` nvme-cli: Plea for help to document fabrics commands 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=1474568868.15303.22.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.