All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Yury Norov <yury.norov@gmail.com>,
	linux-kernel@vger.kernel.org, John Stultz <jstultz@google.com>,
	Stephen Boyd <sboyd@kernel.org>
Cc: "Yury Norov [NVIDIA]" <yury.norov@gmail.com>
Subject: Re: [PATCH RESEND 0/2] clocksource: Use better cpumask API where appropriate
Date: Sat, 14 Jun 2025 20:07:41 +0200	[thread overview]
Message-ID: <87y0tunqmq.ffs@tglx> (raw)
In-Reply-To: <20250614155031.340988-1-yury.norov@gmail.com>

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




      parent reply	other threads:[~2025-06-14 18:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-14 15:50 [PATCH RESEND 0/2] clocksource: Use better cpumask API where appropriate Yury Norov
2025-06-14 15:50 ` [PATCH 1/2] clocksource: Use cpumask_any_but() in clocksource_verify_choose_cpus() Yury Norov
2025-06-14 18:16   ` [tip: timers/core] " tip-bot2 for Yury Norov [NVIDIA]
2025-06-14 15:50 ` [PATCH 2/2] clocksource: Use cpumask_next_wrap() in clocksource_watchdog() Yury Norov
2025-06-14 18:16   ` [tip: timers/core] " tip-bot2 for Yury Norov [NVIDIA]
2025-06-14 18:07 ` Thomas Gleixner [this message]

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=87y0tunqmq.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.