From: Thomas Gleixner <tglx@kernel.org>
To: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Hanabishi <i.r.e.c.c.a.k.u.n+kernel.org@gmail.com>,
Eric Naim <dnaim@cachyos.org>,
stable@vger.kernel.org, linux-tip-commits@vger.kernel.org,
x86@kernel.org, linux-kernel@vger.kernel.org,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [tip: timers/urgent] clockevents: Add missing resets of the next_event_forced flag
Date: Tue, 21 Apr 2026 08:18:56 +0200 [thread overview]
Message-ID: <87mrywdeen.ffs@tglx> (raw)
In-Reply-To: <5cbb14d8-46f9-4197-917f-51da852d7500@leemhuis.info>
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
next prev parent reply other threads:[~2026-04-21 6:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87340xfeje.ffs@tglx>
2026-04-16 19:26 ` [tip: timers/urgent] clockevents: Add missing resets of the next_event_forced flag tip-bot2 for Thomas Gleixner
2026-04-19 15:11 ` Linux regression tracking (Thorsten Leemhuis)
2026-04-21 6:18 ` Thomas Gleixner [this message]
2026-04-21 6:26 ` Thorsten Leemhuis
2026-04-21 6:41 ` Greg KH
2026-04-21 6:42 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mrywdeen.ffs@tglx \
--to=tglx@kernel.org \
--cc=dnaim@cachyos.org \
--cc=i.r.e.c.c.a.k.u.n+kernel.org@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox