Thanks, applied to nvme-4.12 after fixing up the changelog, andadding back the (now slightly modified) WARN_ON for a wrong statein nvme_reset_work.