From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH v2 1/2] nvmetcli: Expose ls to dump UI configuration
Date: Mon, 4 Dec 2017 21:13:22 +0100 [thread overview]
Message-ID: <20171204201322.GE17023@lst.de> (raw)
In-Reply-To: <20171203082535.17663-1-sagi@grimberg.me>
Thanks Sagi,
I've applied both patches.
prev parent reply other threads:[~2017-12-04 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 8:25 [PATCH v2 1/2] nvmetcli: Expose ls to dump UI configuration Sagi Grimberg
2017-12-03 8:25 ` [PATCH v2 2/2] nvmetcli: decorate namespace, subsystem and port UI Sagi Grimberg
2017-12-04 8:33 ` Johannes Thumshirn
2017-12-04 8:32 ` [PATCH v2 1/2] nvmetcli: Expose ls to dump UI configuration Johannes Thumshirn
2017-12-04 20:13 ` Christoph Hellwig [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=20171204201322.GE17023@lst.de \
--to=hch@lst.de \
/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