From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"dave.jiang@intel.com" <dave.jiang@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH] ndctl: add list -M documentation
Date: Thu, 11 May 2017 21:52:32 +0000 [thread overview]
Message-ID: <1494539540.30303.99.camel@hpe.com> (raw)
In-Reply-To: <149453390131.38698.13565665088604739422.stgit@djiang5-desk3.ch.intel.com>
On Thu, 2017-05-11 at 13:18 -0700, Dave Jiang wrote:
> Adding the list --media-errors option to documentation.
>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> ---
> Documentation/ndctl-list.txt | 29 +++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
>
> diff --git a/Documentation/ndctl-list.txt b/Documentation/ndctl-
> list.txt
> index 444a6f9..0ac08a8 100644
> --- a/Documentation/ndctl-list.txt
> +++ b/Documentation/ndctl-list.txt
> @@ -146,6 +146,35 @@ include::xable-region-options.txt[]
> --idle::
> Include idle (not enabled) devices in the listing
The output under EXAMPLE should have "badblock_count".
> +-M::
> +--media-errors::
> + Include media errors (badblocks) in the listing.
badblock_count does not need -M. So, I think the description below
could be put under NOTE or something.
> badblocks_count
> + may count blocks that are not in the data space of the
> namespace
> + for sector mode.
Thanks,
-Toshi
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
prev parent reply other threads:[~2017-05-11 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 20:18 [PATCH] ndctl: add list -M documentation Dave Jiang
2017-05-11 21:52 ` Kani, Toshimitsu [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=1494539540.30303.99.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@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