From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH V2 0/2] nvme-cli: add options to set/get property of NVMf
Date: Wed, 13 Dec 2017 08:34:35 -0700 [thread overview]
Message-ID: <20171213153433.GK11218@localhost.localdomain> (raw)
In-Reply-To: <1513131091-15840-1-git-send-email-guanjunxiong@huawei.com>
On Wed, Dec 13, 2017@10:11:29AM +0800, Guan Junxiong wrote:
> Hi all,
>
> To make it easy to use, this two patches add the support to set/get the
> properties for NVMe over Fabric.
>
> Patch 1/2 makes use of show-regs option which only supports PCIe previously
> to support NVMf.
> Patch 2/2 adds new option named set-property to support setting the property
> of NVMf. IMO, it is the responsibility of kernel to try to avoid malicious
> operation such as setting NRSS from the user space. So I ignore this in
> the nvme-cli.
>
> Welcome any comments.
Thanks, I've applied both with some merge and asciidoc fixups.
prev parent reply other threads:[~2017-12-13 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 2:11 [PATCH V2 0/2] nvme-cli: add options to set/get property of NVMf Guan Junxiong
2017-12-13 2:11 ` [PATCH V2 1/2] nvme-cli: add support to get properties for NVMe over Fabric Guan Junxiong
2017-12-13 2:11 ` [PATCH V2 2/2] nvme-cli: support to set the property " Guan Junxiong
2017-12-13 15:34 ` 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=20171213153433.GK11218@localhost.localdomain \
--to=keith.busch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox