The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: Gabriele Monaco <gmonaco@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Anna-Maria Behnsen <anna-maria@linutronix.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Waiman Long <longman@redhat.com>
Subject: Re: [PATCH v8 7/7] timers: Exclude isolated cpus from timer migration
Date: Fri, 25 Jul 2025 12:55:13 +0200	[thread overview]
Message-ID: <aINikVzeWoKpX0_V@localhost.localdomain> (raw)
In-Reply-To: <381cb8d6b28648dbd5772c6bc0b2f1f10c29b53d.camel@redhat.com>

Le Fri, Jul 25, 2025 at 08:42:19AM +0200, Gabriele Monaco a écrit :
> On Fri, 2025-07-25 at 01:05 +0200, Frederic Weisbecker wrote:
> I assume it's cleaner if I squash it in 7/7 and add a
> Co-developed-by: Frederic Weisbecker <frederic@kernel.org>
> and/or
> Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
> 
> Do you agree?

I would prefer to keep the patch standalone because it's already a
logical change that has its own motivation. It's also invasive and
could potentially cause regression (or improvement) so we want to be
able to bisect to that.

Thanks!

-- 
Frederic Weisbecker
SUSE Labs

      reply	other threads:[~2025-07-25 10:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-14 13:30 [PATCH v8 0/7] timers: Exclude isolated cpus from timer migration Gabriele Monaco
2025-07-14 13:30 ` [PATCH v8 1/7] timers: Rename tmigr 'online' bit to 'available' Gabriele Monaco
2025-07-14 13:30 ` [PATCH v8 2/7] timers: Add the available mask in timer migration Gabriele Monaco
2025-07-24 10:20   ` Frederic Weisbecker
2025-07-14 13:30 ` [PATCH v8 3/7] timers: Use scoped_guard when setting/clearing the tmigr available flag Gabriele Monaco
2025-07-24 10:29   ` Frederic Weisbecker
2025-07-14 13:30 ` [PATCH v8 4/7] cgroup/cpuset: Rename update_unbound_workqueue_cpumask() to update_exclusion_cpumasks() Gabriele Monaco
2025-07-24 10:33   ` Frederic Weisbecker
2025-07-14 13:30 ` [PATCH v8 5/7] sched/isolation: Force housekeeping if isolcpus and nohz_full don't leave any Gabriele Monaco
2025-07-14 13:30 ` [PATCH v8 6/7] cgroup/cpuset: Fail if isolated and nohz_full don't leave any housekeeping Gabriele Monaco
2025-07-24 13:01   ` Frederic Weisbecker
2025-07-14 13:30 ` [PATCH v8 7/7] timers: Exclude isolated cpus from timer migration Gabriele Monaco
2025-07-24 23:05   ` Frederic Weisbecker
2025-07-25  6:42     ` Gabriele Monaco
2025-07-25 10:55       ` Frederic Weisbecker [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=aINikVzeWoKpX0_V@localhost.localdomain \
    --to=frederic@kernel.org \
    --cc=anna-maria@linutronix.de \
    --cc=gmonaco@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --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