23 Dec
2017
23 Dec
'17
9:18 a.m.
On Fri, Dec 22, 2017 at 09:37:48AM -0800, Brian Norris wrote:
included in 4.14-rc1, so something needs to be done in Linus's tree to resolve this issue, otherwise people will hit this as a regression when moving to 4.14 or newer.
Well, I wouldn't object to reverting it in Linus' tree too, since AFAIK, this is something that can be configured by user-space policy, no? And that way, no user space is surprised by the sudden additional requirements on managing bluetooth wakeup.
I agree, please work with the bluetooth developers to make this happen. They seem to be ignoring patches right now, so you might have to kick them a few times :(
thanks
greg k-h