From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>,
"Busch, Keith" <keith.busch@intel.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [ndctl PATCH 2/2] ndctl: Add 'list' verbose documentation
Date: Tue, 26 Jun 2018 22:59:17 +0000 [thread overview]
Message-ID: <1530053956.27147.34.camel@intel.com> (raw)
In-Reply-To: <20180626204649.7665-2-keith.busch@intel.com>
On Tue, 2018-06-26 at 14:46 -0600, Keith Busch wrote:
> Signed-off-by: Keith Busch <keith.busch@intel.com>
> ---
> Documentation/ndctl/ndctl-list.txt | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
I think this can all just go in the first patch?
> diff --git a/Documentation/ndctl/ndctl-list.txt
> b/Documentation/ndctl/ndctl-list.txt
> index 13ebdcd..791638c 100644
> --- a/Documentation/ndctl/ndctl-list.txt
> +++ b/Documentation/ndctl/ndctl-list.txt
> @@ -200,6 +200,18 @@ include::xable-region-options.txt[]
> ]
> }
>
> +-v::
> +--verbose::
> + Increase verbosity of the output. This can be specified
> + multiple times to be even more verbose on the informational and
> + miscellaneous output, and can be used to override the flags for
> + showing specific information.
Should we detail here what verbosity level enables which flags? Or is that
too much upkeep in case things change..
> +
> +[verse]
> +ndctl list -v
> +ndctl list -vv
> +ndctl list -vvv
> +
> include::human-option.txt[]
>
> ----
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2018-06-26 22:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 20:46 [ndctl PATCH 1/2] ndctl: Add 'list' verbose options Keith Busch
2018-06-26 20:46 ` [ndctl PATCH 2/2] ndctl: Add 'list' verbose documentation Keith Busch
2018-06-26 22:59 ` Verma, Vishal L [this message]
2018-06-26 23:20 ` Dan Williams
2018-06-26 21:11 ` [ndctl PATCH 1/2] ndctl: Add 'list' verbose options Dan Williams
2018-06-26 22:37 ` Keith Busch
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=1530053956.27147.34.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=dan.j.williams@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-nvdimm@lists.01.org \
/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