Re: [PATCH resend 0/6] Fix cdrom autoclose

On Fri, 26 Jan 2018 12:04:56 -0800 James Bottomley wrote: > On Fri, 2018-01-26 at 17:58 +0100, Michal Suchanek wrote: > > First time I did not get any feedback for the patches. > > This is likely because no-one who might inspect the code saw the > patches ... what

Re: [PATCH resend 0/6] Fix cdrom autoclose

On Fri, 26 Jan 2018 12:04:56 -0800 James Bottomley wrote: > On Fri, 2018-01-26 at 17:58 +0100, Michal Suchanek wrote: > > First time I did not get any feedback for the patches. > > This is likely because no-one who might inspect the code saw the > patches ... what list are they going to?  I'm

Re: [PATCH resend 0/6] Fix cdrom autoclose

On Fri, 2018-01-26 at 17:58 +0100, Michal Suchanek wrote: > First time I did not get any feedback for the patches. This is likely because no-one who might inspect the code saw the patches ... what list are they going to?  I'm on the block, scsi and ide mailing lists and I only saw a doc patch the

Re: [PATCH resend 0/6] Fix cdrom autoclose

On Fri, 2018-01-26 at 17:58 +0100, Michal Suchanek wrote: > First time I did not get any feedback for the patches. This is likely because no-one who might inspect the code saw the patches ... what list are they going to?  I'm on the block, scsi and ide mailing lists and I only saw a doc patch the

[PATCH resend 0/6] Fix cdrom autoclose

Hello, there is cdrom autoclose feature that is supposed to close the tray, wait for the disc to become ready, and then open the device. This used to work in ancient times. Then in old times there was a hack in util-linux which worked around the breakage which probably resulted from

[PATCH resend 0/6] Fix cdrom autoclose

Hello, there is cdrom autoclose feature that is supposed to close the tray, wait for the disc to become ready, and then open the device. This used to work in ancient times. Then in old times there was a hack in util-linux which worked around the breakage which probably resulted from