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

Reply via email to