On Fri, Jan 1, 2021 at 12:19 PM James Bottomley
<James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Originally this change was slated for the merge window but a late
> arriving build problem with CONFIG_PM=n derailed that.
So I've pulled this, but we need to have a policy for reverting this
quickly if it turns out to cause problems.
I'm not worried about any remaining build issues - but I'm simply
worried about some missed case where code depended on the block layer
passing commands through even while suspended.
The block bits would seem affect non-SCSI stuff too, how extensively
have any random odd special case been tested?
So I'm not so much with you on the "the scary case is the spi domain
validation case". I'm more about "what about all the other random
cases for random special drivers"
Linus
