From: Thomas Gleixner <tglx@kernel.org>
To: Zhan Xusheng <zhanxusheng1024@gmail.com>
Cc: linux-kernel@vger.kernel.org, Zhan Xusheng <zhanxusheng@xiaomi.com>
Subject: Re: [PATCH] clockevents: Reset next_event_forced in the coupled programming path
Date: Mon, 27 Apr 2026 17:08:29 +0200 [thread overview]
Message-ID: <87eck0zbiq.ffs@tglx> (raw)
In-Reply-To: <20260427092824.48335-1-zhanxusheng@xiaomi.com>
On Mon, Apr 27 2026 at 17:28, Zhan Xusheng wrote:
> All successful event programming paths in clockevents_program_event()
> reset next_event_forced to zero, except the clockevent_set_next_coupled()
> path which was added before the starvation prevention mechanism.
>
> Add the missing reset for consistency.
What for?
It never reaches the point where it sets or checks that
next_event_forced bit.
Your AI slop is clearly not getting it.
next prev parent reply other threads:[~2026-04-27 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 9:28 [PATCH] clockevents: Reset next_event_forced in the coupled programming path Zhan Xusheng
2026-04-27 15:08 ` Thomas Gleixner [this message]
2026-04-28 2:23 ` Zhan Xusheng
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=87eck0zbiq.ffs@tglx \
--to=tglx@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhanxusheng1024@gmail.com \
--cc=zhanxusheng@xiaomi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.