From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] NVMe-CLI Fix command failures in regress script
Date: Fri, 2 Feb 2018 14:38:29 -0700 [thread overview]
Message-ID: <20180202213829.GL24417@localhost.localdomain> (raw)
In-Reply-To: <MWHPR04MB102561D215C063C6967513F4EAF90@MWHPR04MB1025.namprd04.prod.outlook.com>
On Fri, Feb 02, 2018@09:33:12PM +0000, Jeffrey Lien wrote:
> Keith,
> Then should we remove the commands that require a namespace id (ie id-ns, flush, write, and read)?
If you provide a block device, nvme-cli will automatically figure out
the nsid if you didn't provide one.
next prev parent reply other threads:[~2018-02-02 21:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 19:50 [PATCH] NVMe-CLI Fix command failures in regress script Jeff Lien
2018-02-02 20:29 ` Keith Busch
2018-02-02 21:33 ` Jeffrey Lien
2018-02-02 21:38 ` Keith Busch [this message]
2018-02-05 16:49 ` Jeffrey Lien
2018-02-05 16:57 ` Keith Busch
2018-02-05 19:00 ` Jeffrey Lien
2018-02-05 19:34 ` Keith Busch
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=20180202213829.GL24417@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