Hello > Hmmm. 6.8 final is due. Is that something we can live with? Or would it be > a good idea to revert above commit for now and reapply it when something > better emerged? I doubt that the answer is "yes, let's do that", but I > have to ask. I couldn't find better way now. I think it's better to follow you mentioned > > Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) > -- > Everything you wanna know about Linux kernel regression tracking: > https://protect2.fireeye.com/v1/url?k=1721f6f7-48bacfe8-17207db8- > 000babdfecba-6a9835eff37b0303&q=1&e=f39e15ee-403b-4efb-a56e- > f6aba3905bc5&u=https%3A%2F%2Flinux- > regtracking.leemhuis.info%2Fabout%2F%23tldr > If I did something stupid, please tell me, as explained on that page. > > P.S.: To be sure the issue doesn't fall through the cracks unnoticed, I'm > adding it to regzbot, the Linux kernel regression tracking bot: > > #regzbot report / > #regzbot introduced 22a9d9585812440211b > #regzbot duplicate: https://lore.kernel.org/lkml/ZYhQ2-OnjDgoqjvt@xxxxxxx/ > #regzbot title dmaengine: CPU stalls while loading bluetooth module > #regzbot ignore-activity
