[PATCHv2] nvme: send uevent once a multipath namespace is operational again

[Sagi Grimberg]

> In an all paths down scenario I/O will be requeued or aborted, and no
> further I/O will be ongoing on this namespace.
> This leaves the upper layers unable to determine if the namespace
> becomes operational again eg. after a successful controller reset.

Who is upper-layers here?

> With this patch a 'change' uevent will be sent per multipathed namespace
> once the underlying controller moved to LIVE and started I/O processing
> by calling nvme_kick_requeue_lists().
> 

Other than that looks reasonable to me..