From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH V3 2/2] nvme-cli: add ana-log documentation
Date: Fri, 03 Aug 2018 20:59:57 +0900 [thread overview]
Message-ID: <1533297597.2982.12.camel@gmail.com> (raw)
In-Reply-To: <20180802032819.6558-3-chaitanya.kulkarni@wdc.com>
Hi Chaitanya,
Here's my review on this doc.
On 18-08-01 20:28:19, Chaitanya Kulkarni wrote:
> Signed-off-by: Chaitanya Kulkarni <chaitanya.kulkarni at wdc.com>
> Reviewed-by: Hannes Reinecke <hare at suse.com>
> ---
> diff --git a/Documentation/nvme-ana-log.txt b/Documentation/nvme-ana-log.txt
> new file mode 100644
> index 0000000..3514504
> --- /dev/null
> +++ b/Documentation/nvme-ana-log.txt
> @@ -0,0 +1,45 @@
> +nvme-ana-log(1)
> +===============
> +
> +NAME
> +----
> +nvme-ana-log - Send NVMe ANA log page request, returns result and log
> +
> +SYNOPSIS
> +--------
> +[verse]
> +'nvme ana-log' <device>
This verse can have argument options like all the other docs.
'nvme ana-log' <device> [-o <fmt> | --output-format=<fmt>]
> +
> +DESCRIPTION
> +-----------
> +Retrieves the NVMe Asymmetric Namespace Access log page from an NVMe device
> +and provides the returned structure.
> +
> +The <device> parameter is mandatory NVMe character device (ex: /dev/nvme0).
> +
> +On success, the returned ANA log structure may be returned in one of
> +several ways depending on the option flags; the structure may parsed by
> +the program and printed in a readable format or the raw buffer may be
> +printed to stdout for another program to parse.
> +
> +OPTIONS
> +-------
> +-b::
> +--raw-binary::
> + Print the raw ANA log buffer to stdout.
> +
It can be deprecated due to a reason mentioned in the first patch comment.
> +-o <format>::
> +--output-format=<format>::
> +??????????????Set the reporting format to 'normal', 'json', or
> +??????????????'binary'. Only one output format can be used at a time.
> +
> +EXAMPLES
> +--------
> +* Print the ANA log page in a human readable format:
> +------------
> +# nvme ana-log /dev/nvme0
> +------------
> +
> +NVME
> +----
> +Part of the nvme-user suite
> --?
> 2.17.0
Thanks,
Minwoo Im
prev parent reply other threads:[~2018-08-03 11:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 3:28 [PATCH V3 0/2] nvme-cli: add ana-log page support Chaitanya Kulkarni
2018-08-02 3:28 ` [PATCH V3 1/2] nvme-cli: add minimal " Chaitanya Kulkarni
2018-08-03 10:18 ` Minwoo Im
2018-08-03 11:59 ` Minwoo Im
2018-08-02 3:28 ` [PATCH V3 2/2] nvme-cli: add ana-log documentation Chaitanya Kulkarni
2018-08-03 11:59 ` Minwoo Im [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=1533297597.2982.12.camel@gmail.com \
--to=minwoo.im.dev@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).