From: Thomas Gleixner <tglx@linutronix.de>
To: Yury Norov <yury.norov@gmail.com>
Cc: linux-kernel@vger.kernel.org, John Stultz <jstultz@google.com>,
Stephen Boyd <sboyd@kernel.org>
Subject: Re: [PATCH 1/2] clocksource: Fix opencoded cpumask_any_but() in clocksource_verify_choose_cpus()
Date: Tue, 10 Jun 2025 11:03:44 +0200 [thread overview]
Message-ID: <87wm9knf2n.ffs@tglx> (raw)
In-Reply-To: <aEbwsyJyqm7WYJkJ@yury>
On Mon, Jun 09 2025 at 10:33, Yury Norov wrote:
> On Mon, Jun 09, 2025 at 12:03:23PM +0200, Thomas Gleixner wrote:
>> On Sat, Jun 07 2025 at 10:11, Yury Norov wrote:
>>
>> Why are you so obsessed to slap 'Fix' on every subject line?
>>
>> This fixes absolutely nothing at all.
>
> Opencoding helpers is an error, isn't? That's why 'fix'.
It's not. It's functionally correct, so there is no error. It's an
oversight in terms of code efficiency, not more.
next prev parent reply other threads:[~2025-06-10 9:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-07 14:11 [PATCH 0/2] clocksource: Use better cpumask API where appropriate Yury Norov
2025-06-07 14:11 ` [PATCH 1/2] clocksource: Fix opencoded cpumask_any_but() in clocksource_verify_choose_cpus() Yury Norov
2025-06-09 10:03 ` Thomas Gleixner
2025-06-09 14:33 ` Yury Norov
2025-06-10 9:03 ` Thomas Gleixner [this message]
2025-06-07 14:11 ` [PATCH 2/2] clocksource: Fix opencoded cpumask_next_wrap() Yury Norov
-- strict thread matches above, loose matches on Subject: below --
2025-06-04 23:25 [PATCH 0/2] clocksource: use better cpumask API where appropriate Yury Norov
2025-06-04 23:25 ` [PATCH 1/2] clocksource: fix opencoded cpumask_any_but() in clocksource_verify_choose_cpus() Yury Norov
2025-06-05 18:13 ` John Stultz
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=87wm9knf2n.ffs@tglx \
--to=tglx@linutronix.de \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=yury.norov@gmail.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.