All of lore.kernel.org
 help / color / mirror / Atom feed
From: chengjike <chengjike.cheng@huawei.com>
To: <kbusch@kernel.org>, <linux-nvme@lists.infradead.org>,
	<sagi@grimberg.me>,  <chaitanyak@nvidia.com>
Cc: <sunao.sun@huawei.com>, <jiangtao62@huawei.com>
Subject: [PATCH V3 nvme-cli 0/2] add "Path Access" field in command "nvme list"
Date: Tue, 28 Sep 2021 16:50:48 +0800	[thread overview]
Message-ID: <20210928085050.4141-1-chengjike.cheng@huawei.com> (raw)


This patch V3 is to add "Path Access" field in command "nvme list".
Changes on this V3 since the last version of this
 - updated the commit log by Chaitanya Kulkarni
 - added a function comment by Chaitanya Kulkarni
 - modified the inappropriate code by Chaitanya Kulkarni

patch V2
https://lore.kernel.org/linux-nvme/20210927014137.3756-1-chengjike.cheng@huawei.com/T/#t

chengjike (1):
  initialize disk "access" variable

 src/nvme/private.h |  1 +
 src/nvme/tree.c    | 54 +++++++++++++++++++++++++++++++++++++++++-----
 src/nvme/tree.h    | 11 ++++++++++
 3 files changed, 61 insertions(+), 5 deletions(-)

chengjike (1):
  add "Path Access" entry in command output

 nvme-print.c | 15 +++++++++------
 1 file changed, 9 insertions(+), 6 deletions(-)
 
-- 
2.21.0.windows.1


_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

             reply	other threads:[~2021-09-28  9:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28  8:50 chengjike [this message]
2021-09-28  8:50 ` [PATCH V3 nvme-cli 1/2] initialize disk "access" variable chengjike
2021-09-28 20:45   ` Sagi Grimberg
2021-09-28 21:18     ` Chaitanya Kulkarni
2021-10-08 12:23     ` Chengjike (ISSP)
2021-09-28  8:50 ` [PATCH V3 nvme-cli 2/2] add "Path Access" entry in command output chengjike

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=20210928085050.4141-1-chengjike.cheng@huawei.com \
    --to=chengjike.cheng@huawei.com \
    --cc=chaitanyak@nvidia.com \
    --cc=jiangtao62@huawei.com \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    --cc=sunao.sun@huawei.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.