From mboxrd@z Thu Jan  1 00:00:00 1970
From: hch@infradead.org (Christoph Hellwig)
Date: Wed, 1 Nov 2017 09:29:31 -0700
Subject: [PATCH 0/5] nvmet/nvmet_fc: add events for discovery controller
 rescan
In-Reply-To: <7afaa043-221e-cfcc-1c02-4916efa12a66@gmail.com>
References: <20171028172114.2045-1-jsmart2021@gmail.com>
 <20171101153640.GA13553@infradead.org>
 <d6d14ba1-b17f-f635-5235-0115170b01f1@gmail.com>
 <20171101155711.GA4591@infradead.org>
 <7afaa043-221e-cfcc-1c02-4916efa12a66@gmail.com>
Message-ID: <20171101162931.GB15827@infradead.org>

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.