From: keith.busch@linux.intel.com (Keith Busch)
Subject: [PATCH] nvme-cli: Implemented primary and secondary controller
Date: Tue, 19 Jun 2018 09:54:38 -0600 [thread overview]
Message-ID: <20180619155438.GD19922@localhost.localdomain> (raw)
In-Reply-To: <20180619154317.GA1638@infradead.org>
On Tue, Jun 19, 2018@08:43:17AM -0700, Christoph Hellwig wrote:
> Btw, I'm really unconfortable with having this code around if it
> hasn't actually been tested..
Agreed. If you can't test it, it probably doesn't work.
next prev parent reply other threads:[~2018-06-19 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 15:28 [PATCH] nvme-cli: Implemented primary and secondary controller Revanth Rajashekar
2018-06-19 15:45 ` Keith Busch
2018-06-19 15:43 ` Christoph Hellwig
2018-06-19 15:54 ` Keith Busch [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-18 23:12 Revanth Rajashekar
2018-06-19 14:13 ` Keith Busch
2018-06-18 21:28 Revanth Rajashekar
2018-06-18 21:57 ` 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=20180619155438.GD19922@localhost.localdomain \
--to=keith.busch@linux.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 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.