From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvme: Correct NVMF enum values to match NVMe-oF rev 1.0
Date: Thu, 2 Mar 2017 07:56:13 -0800 [thread overview]
Message-ID: <20170302155613.GA9623@infradead.org> (raw)
In-Reply-To: <20170302160227.GD14852@localhost.localdomain>
On Thu, Mar 02, 2017@11:02:27AM -0500, Keith Busch wrote:
> On Thu, Mar 02, 2017@07:52:42AM -0800, Christoph Hellwig wrote:
> > So this basically affects the discovery information, which at least
> > in the Linux world is not used anywhere except for printing it in
> > nvme-cli. So this looks fine:
> >
> > Reviewed-by: Christoph Hellwig <hch at lst.de>
> >
> > But can you also send an update for nvme-cli, please?
>
> Yep, that's done: https://github.com/linux-nvme/nvme-cli/pull/161
Grr, damn github pull requests that defeat review..
next prev parent reply other threads:[~2017-03-02 15:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 2:22 [PATCH] nvme: Correct NVMF enum values to match NVMe-oF rev 1.0 Roland Dreier
2017-03-02 15:52 ` Christoph Hellwig
2017-03-02 16:02 ` Keith Busch
2017-03-02 15:56 ` Christoph Hellwig [this message]
2017-03-02 18:08 ` Roland Dreier
2017-03-02 18:34 ` Keith Busch
2017-03-02 19:04 ` Roland Dreier
2017-03-03 15:52 ` Schremmer, Steven
2017-03-06 11:43 ` Sagi Grimberg
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=20170302155613.GA9623@infradead.org \
--to=hch@infradead.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 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.