All of lore.kernel.org
 help / color / mirror / Atom feed
From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH 1/2] nvme-cli: add fields into identify controller data structure
Date: Fri, 2 Jun 2017 22:25:47 -0700	[thread overview]
Message-ID: <20170603052547.GB14365@infradead.org> (raw)
In-Reply-To: <e704f915-f08f-6fe9-1132-81d7b6845c7d@163.com>

On Sat, Jun 03, 2017@11:08:54AM +0800, guanjx09 wrote:
> Hi,Christoph
> 
> On Friday, June 02, 2017 03:46 PM, Christoph Hellwig wrote:
> > Please also add them to the kernel copy of the header so that they
> > stay in sync.  Except for that his looks fine to me:
> > 
> > Reviewed-by: Christoph Hellwig <hch at lst.de>
> > 
> 
> Here is the patch which adds those fields into nvme_id_ctrl structure
> in the kernel copy of the header. Does it looks good?

It does.  I'll apply it once the branch for Linux 4.13 is open.

  reply	other threads:[~2017-06-03  5:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02  7:18 [PATCH 0/2]nvme-cli: id-ctrl supports NVMe 1.3 spec Guan Junxiong
2017-06-02  7:18 ` [PATCH 1/2] nvme-cli: add fields into identify controller data structure Guan Junxiong
2017-06-02  7:46   ` Christoph Hellwig
2017-06-03  3:08     ` guanjx09
2017-06-03  5:25       ` Christoph Hellwig [this message]
     [not found]     ` <71e89de.8c54.15c69866ff6.Coremail.guanjx09@163.com>
2017-06-03  5:25       ` Christoph Hellwig
2017-06-04 15:20         ` Sagi Grimberg
2017-06-12 16:11         ` Christoph Hellwig
2017-06-13  1:31           ` Guan Junxiong
2017-06-04 15:20   ` Sagi Grimberg
2017-06-02  7:18 ` [PATCH 2/2] nvme-cli: show more fields for id-ctrl Guan Junxiong
2017-06-02  7:46   ` Christoph Hellwig
2017-06-04 15:22   ` Sagi Grimberg
2017-06-12 14:30   ` Keith Busch
2017-06-13  1:37     ` Guan Junxiong

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=20170603052547.GB14365@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.