On Fri, Mar 25, 2022 at 8:09 AM Greg Kroah-Hartman
<gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
>
> From: Halil Pasic <pasic@xxxxxxxxxxxxx>
>
> commit aa6f8dcbab473f3a3c7454b74caa46d36cdc5d13 upstream.
This one causes a regression on at least some wireless drivers
(ath9k). There's some active discussion about it, maybe it gets
reverted, maybe there are other options.
There's an ath9k patch that fixes the problem, so if this patch goes
into the stable tree the ath9k fix will follow.
But it might be a good idea to simply hold off on this patch a bit,
because that ath9k patch hasn't actually landed yet, there's some
discussion about it all, and it's not clear that other drivers might
not have the same issue.
So I'm not NAK'ing this patch from stable, but I also don't think it's
timing-critical, and it might be a good idea to delay it for a week or
two to both wait for the ath9k patch and to see if something else
comes up.
Linus
