V2: 1. Use cancel_work_sync instead of introducing new state (Sagi)
     2. Skip using NVME_CTRL_SCHED_RESET state (Sagi)
V1: nvme_probe set RESETTING state and check for NVME_CTRL_RESETTING
     state in nvme_should_reset instead of work_busy (hch)

This type of information should come after the '---' separator
so git history won't keep it forever.

Fixes: c5f6ce97c1210 ("nvme: don't schedule multiple resets")
Signed-off-by: Rakesh Pandit <[email protected]>
---
Other than that,

Reviewed-by: Sagi Grimberg <[email protected]>

Reply via email to