[v1] clocksource: Use better cpumask API where appropriate

[PATCH RESEND 0/2] clocksource: Use better cpumask API where appropriate

Posted by Yury Norov 3 months, 3 weeks ago

From: Yury Norov [NVIDIA] <yury.norov@gmail.com>

The dedicated API works better and improves on readability

Resend: drop 'fix opencoded...' wording (Tomas)
v2: https://lore.kernel.org/all/20250607141106.563924-1-yury.norov@gmail.com/
v1: https://lore.kernel.org/all/20250604232550.40491-1-yury.norov@gmail.com/

Yury Norov [NVIDIA] (2):
  clocksource: Use cpumask_any_but() in clocksource_verify_choose_cpus()
  clocksource: Use cpumask_next_wrap() in clocksource_watchdog()

 kernel/time/clocksource.c | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

-- 
2.43.0

Re: [PATCH RESEND 0/2] clocksource: Use better cpumask API where appropriate

Posted by Thomas Gleixner 3 months, 3 weeks ago

On Sat, Jun 14 2025 at 11:50, Yury Norov wrote:
> From: Yury Norov [NVIDIA] <yury.norov@gmail.com>
>
> The dedicated API works better and improves on readability
>
> Resend: drop 'fix opencoded...' wording (Tomas)

This is not a resend as you changed the change log, so it's V3.

Resend is only for unmodified versions where you got no feedback and did
not change anything.

And in the RESEND case you have to keep the version number so stuff can
be identified as resend of a particular version.

People have scripts which depend on submitters following the
rules. Chasing stuff by hand is just waste of time.

Thanks,

        tglx