On Fri, Sep 17 2021 at 00:32, Thomas Gleixner wrote:
> I usually spend quite some time on tagging patches for stable and it's
> annoying me that this patch got reverted while stuff which I explicitely
> did not tag for stable got backported for whatever reason and completely
> against the stable rules:
>
> 627ef5ae2df8 ("hrtimer: Avoid double reprogramming in __hrtimer_start_range_ns()")
>
> What the heck qualifies this to be backported?
>
> 1) It's hot of the press and just got merged in the 5.15-rc1 merge
> window and is not tagged for stable
>
> 2) https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
>
> clearly states the rules but obviously our new fangled "AI" driven
> approach to select patches for stable is blissfully ignorant of
> these rules. I assume that AI stands for "Artifical Ignorance' here.
>
> I already got a private bug report vs. that on 5.10.65. Annoyingly
> 5.10.5 does not have the issue despite the fact that the resulting diff
5.14.5 obviously...
> between those two versions in hrtimer.c is just in comments.
>
> Bah!
>
> Thanks,
>
> tglx
