From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH 0/5] nvmet/nvmet_fc: add events for discovery controller rescan
Date: Wed, 1 Nov 2017 09:29:31 -0700 [thread overview]
Message-ID: <20171101162931.GB15827@infradead.org> (raw)
In-Reply-To: <7afaa043-221e-cfcc-1c02-4916efa12a66@gmail.com>
On Wed, Nov 01, 2017@09:12:00AM -0700, James Smart wrote:
> Seriously ? It is in a published transport spec that was reviewed by
> working group leadership and members.
NVMe-FC has _never_ been reviewed or even posted to the NVMe technical
working group list. Which is a big part of all the problems it has been
causing. The whole idea of doing a NVMe transport outside of NVMe has
been nothing but a nightmare.
next prev parent reply other threads:[~2017-11-01 16:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-28 17:21 [PATCH 0/5] nvmet/nvmet_fc: add events for discovery controller rescan James Smart
2017-10-28 17:21 ` [PATCH 1/5] nvmet: call transport on subsystem add and delete James Smart
2017-10-28 17:21 ` [PATCH 2/5] nvmet_fc: support transport subsystem events James Smart
2017-10-28 17:21 ` [PATCH 3/5] lpfc: Add support to generate RSCN events for nport James Smart
2017-10-28 17:21 ` [PATCH 4/5] lpfc: Add NVME rescan support via RSCNs James Smart
2017-10-28 17:21 ` [PATCH 5/5] lpfc: Add sysfs interface to post NVME RSCN James Smart
2017-11-02 20:09 ` Ewan D. Milne
2017-11-02 22:02 ` James Smart
2017-10-29 16:11 ` [PATCH 0/5] nvmet/nvmet_fc: add events for discovery controller rescan Sagi Grimberg
2017-10-30 4:43 ` James Smart
2017-11-01 15:38 ` Christoph Hellwig
2017-11-01 16:03 ` James Smart
2017-11-01 16:28 ` Christoph Hellwig
2017-11-01 15:36 ` Christoph Hellwig
2017-11-01 15:55 ` James Smart
2017-11-01 15:57 ` Christoph Hellwig
2017-11-01 16:12 ` James Smart
2017-11-01 16:29 ` Christoph Hellwig [this message]
[not found] <20171029011456.12885-1-jsmart2021@gmail.com>
2017-10-31 12:22 ` Martin K. Petersen
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=20171101162931.GB15827@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).