Re: [tip: timers/urgent] clockevents: Add missing resets of the next_event_forced flag

[Thomas Gleixner <tglx@kernel.org>]

On Sun, Apr 19 2026 at 17:11, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 4/16/26 21:26, tip-bot2 for Thomas Gleixner wrote:
>> The following commit has been merged into the timers/urgent branch of tip:
>> 
>> Commit-ID:     4096fd0e8eaea13ebe5206700b33f49635ae18e5
>> Gitweb:        https://git.kernel.org/tip/4096fd0e8eaea13ebe5206700b33f49635ae18e5
>> Author:        Thomas Gleixner <tglx@kernel.org>
>> AuthorDate:    Tue, 14 Apr 2026 22:55:01 +02:00
>> Committer:     Thomas Gleixner <tglx@kernel.org>
>> CommitterDate: Thu, 16 Apr 2026 21:22:04 +02:00
>> 
>> clockevents: Add missing resets of the next_event_forced flag
>
> Just wondering: what's the plan to mainline this? I wonder if this is
> worth mainlining rather quickly and the tell the stable team right
> afterwards to queue it up for 7.0.1, as in addition to the two affected
> people in this thread (one of which stated that "several users from
> CachyOS reported this regression as well") I noticed three more 7.0 bug
> reports in the past few days that likely are fixed by the quoted patch:

It's in Linus tree and I asked the stable folks to withhold the original
patch which it fixes, so they can queue both at once.

Thanks,

        tglx