Comment 15 for bug 1642903

> Note that there is a current SRU in trusty which blocks this.

is that current SRU for bug 1562344?

> But this being "wishlist" it's not
> that urgent anyway,

This isn't really wishlist, this is needed to persistently identify NVMe drives on systems with multiple drives.

> and my gut feeling is that it's okay to wait a bit until we get some more
> fixes queued up?

I'd like to see this patch get started in trusty-proposed sooner than later, is it possible to go ahead with this for trusty? (and can we also add the workaround patch for bug 1647485?)