Linux-NVDIMM Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <keith.busch@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: [ndctl PATCH 1/2] ndctl: Add 'list' verbose options
Date: Tue, 26 Jun 2018 16:37:03 -0600	[thread overview]
Message-ID: <20180626223702.GA7824@localhost.localdomain> (raw)
In-Reply-To: <CAPcyv4gaGsufzXc9KNaTnrHJU+Mf+eQtFW=7ENmMdGNh9LNK4A@mail.gmail.com>

On Tue, Jun 26, 2018 at 02:11:30PM -0700, Dan Williams wrote:
> This turns on listing DIMMs even if --dimms was not specified on the
> command line. I was thinking not until level 2 do we start turning on
> more device objects beyond what is specified. For example "ndctl list
> -v" is the same as "ndctl list" that lists namespaces by default.
> However it goes further to turn on extra / namespace-relative data
> like 'raw_uuid' and 'sector_size' but also data like "--media-errors"
> and "--dax". Then it follows commands like "ndctl list -Dv" list the
> DIMMs and turns on optional fields like 'handle' and 'phys_id' in
> addition to "--health" information.

Aha, that makes more sense. Thanks for the info.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

      reply	other threads:[~2018-06-26 22:33 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
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 [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=20180626223702.GA7824@localhost.localdomain \
    --to=keith.busch@intel.com \
    --cc=dan.j.williams@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