mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yury Norov <yury.norov@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
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: Mon, 9 Jun 2025 10:33:23 -0400	[thread overview]
Message-ID: <aEbwsyJyqm7WYJkJ@yury> (raw)
In-Reply-To: <8734c9p6z8.ffs@tglx>

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'.
 
> All it does is to replace a open coded sequence by appropriate
> function. So describe the changes accurately.

I'm not attached to words. If you prefer 'replace', I can resend with
the wording you like. Please advise.

Thanks,
Yury

  reply	other threads:[~2025-06-09 14:33 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 [this message]
2025-06-10  9:03       ` Thomas Gleixner
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=aEbwsyJyqm7WYJkJ@yury \
    --to=yury.norov@gmail.com \
    --cc=jstultz@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sboyd@kernel.org \
    --cc=tglx@linutronix.de \
    /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
all inboxes | Powered by JetHome®