From: keith.busch@linux.intel.com (Keith Busch)
Subject: [PATCH 0/6] nvme-cli fixes and ANA updates
Date: Fri, 17 Aug 2018 15:58:59 -0600 [thread overview]
Message-ID: <20180817215859.GC9931@localhost.localdomain> (raw)
In-Reply-To: <20180817072908.56784-1-hare@suse.de>
On Fri, Aug 17, 2018@09:29:02AM +0200, Hannes Reinecke wrote:
> Hi Keith,
>
> here's a small set of fixes and an update to have nvme list-subsys printing
> out the ANA state for all paths.
> This brings nvme-cli output on par with that from multipath-tools.
>
> As usual, comments and reviews welcome.
These all look fine to me. I'll apply 1-3 immediately as those look
pretty trivial. I'll give a test on 4-6 early next week when I should
have more time for nvme again.
prev parent reply other threads:[~2018-08-17 21:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 7:29 [PATCH 0/6] nvme-cli fixes and ANA updates Hannes Reinecke
2018-08-17 7:29 ` [PATCH 1/6] nvme-ana-log: fixup compiler warning in show_ana_log() Hannes Reinecke
2018-08-17 8:09 ` Christoph Hellwig
2018-08-17 21:44 ` Chaitanya Kulkarni
2018-08-17 21:55 ` Keith Busch
2018-08-17 7:29 ` [PATCH 2/6] nvme-vendor: fixup c99 declaration in huawei plugin Hannes Reinecke
2018-08-17 8:09 ` Christoph Hellwig
2018-08-17 21:56 ` Keith Busch
2018-08-17 7:29 ` [PATCH 3/6] nvme-discover: sanitize options Hannes Reinecke
2018-08-17 8:10 ` Christoph Hellwig
2018-08-17 7:29 ` [PATCH 4/6] nvme-discover: Retry discovery log if the generation counter changes Hannes Reinecke
2018-08-17 8:11 ` Christoph Hellwig
2018-08-17 10:06 ` Hannes Reinecke
2018-08-17 7:29 ` [PATCH 5/6] nvme-list-subsys: Print PCIe controller address Hannes Reinecke
2018-08-17 8:12 ` Christoph Hellwig
2018-08-17 10:06 ` Hannes Reinecke
2018-08-17 7:29 ` [PATCH 6/6] nvme-list-subsys: Add device name argument and print out ANA state Hannes Reinecke
2018-08-17 8:12 ` Christoph Hellwig
2018-08-17 22:14 ` Chaitanya Kulkarni
2018-08-17 21:58 ` 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=20180817215859.GC9931@localhost.localdomain \
--to=keith.busch@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.