Re: [PATCH] clockevents: Reset next_event_forced in the coupled programming path

[Zhan Xusheng]

On Mon, 27 Apr 2026 at 17:08, Thomas Gleixner <tglx@xxxxxxxxxx> wrote:
> What for?
>
> It never reaches the point where it sets or checks that
> next_event_forced bit.

You're right. Devices using the coupled path never reach the code
which sets or checks next_event_forced, so this reset is dead code.

Sorry for the noise.

Zhan Xusheng