nvme-4.14 rebased
Christoph Hellwig
maintainerHi all,
I've rebased the nvme-4.14 branch on top of the nvme-4.13 branch to avoid conflicts. As part of that I made the timestamp set features return an error similar to the other reset fixes.
Jon: can you double check the change is correct?
Quoted 8 lines · Christoph Hellwig
Hi all,
I've rebased the nvme-4.14 branch on top of the nvme-4.13 branch to avoid conflicts. As part of that I made the timestamp set features return an error similar to the other reset fixes.
Jon: can you double check the change is correct?
Hi Christoph,
The only thing I'd suggest is not letting a failure to set the timestamp be a failure to initialize the controller.
Regards,
Jon
Quoted 7 lines · Jon Derrick
Quoted 6 lines · Christoph Hellwig
Hi all,
I've rebased the nvme-4.14 branch on top of the nvme-4.13 branch to avoid conflicts. As part of that I made the timestamp set features return an error similar to the other reset fixes.
Quoted 7 lines
Quoted 2 lines
Jon: can you double check the change is correct?
Hi Christoph,
The only thing I'd suggest is not letting a failure to set the timestamp be a failure to initialize the controller.
It looks like Christoph just has it fail initialization if the timestamp feature command never gets a controller response. We actually do need to abandon controller init in that case since the controller is disabled in the timeout handler.