[PATCH 17/18] nvme: move namespace scanning to common code

[Christoph Hellwig]

On Thu, Oct 22, 2015 at 09:24:25PM +0000, Busch, Keith wrote:
> It does fall through to the older way if identify list fails. My concern
> is when it doesn't fail when it should have. Some controllers claim 1.1 or
> higher, but do not interpret the Identify Namespace List correctly. They
> just check that CNS != 0, and if true, returns success with an Identify
> Namespace structure, so the driver misinterprets the data.
> 
> I filed bugs with the vendors I know about, but there may be others I
> haven't tested.

Can you blacklist the known bad controller using the quirks mechanism
I added during the driver split?