public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: Yury Norov <yury.norov@gmail.com>
Cc: Gabriele Monaco <gmonaco@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v12 8/9] cpumask: Add initialiser CPUMASK_NULL to use cleanup helpers
Date: Tue, 16 Sep 2025 13:27:36 +0200	[thread overview]
Message-ID: <aMlJqDjWNyak07LX@localhost.localdomain> (raw)
In-Reply-To: <aMhcYCCJDFWoxcyw@yury>

Le Mon, Sep 15, 2025 at 02:35:12PM -0400, Yury Norov a écrit :
> On Mon, Sep 15, 2025 at 05:02:45PM +0000, Gabriele Monaco wrote:
> > 2025-09-15T16:04:53Z Yury Norov <yury.norov@gmail.com>:
> > > So why don't you pick the original patch instead?
> > 
> > In my opinion, the /juice/ of that patch was included with [1], here I'm just adding part of it.
> > If you prefer I can pick that patch and adapt the commit message to reflect only the part included here.
> > 
> > [1] - https://lore.kernel.org/lkml/1706509267-17754-3-git-send-email-schakrabarti@linux.microsoft.com/
> 
> Yes please.

And can we rename CPUMASK_NULL to CPUMASK_VAR_NULL to avoid accidents/confusion with real
cpumasks initializations?

Thanks.

-- 
Frederic Weisbecker
SUSE Labs

  reply	other threads:[~2025-09-16 11:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15 14:59 [PATCH v12 0/9] timers: Exclude isolated cpus from timer migration Gabriele Monaco
2025-09-15 14:59 ` [PATCH v12 1/9] timers/migration: Postpone online/offline callbacks registration to late initcall Gabriele Monaco
2025-09-15 14:59 ` [PATCH v12 2/9] timers: Rename tmigr 'online' bit to 'available' Gabriele Monaco
2025-09-15 14:59 ` [PATCH v12 3/9] timers: Add the available mask in timer migration Gabriele Monaco
2025-09-15 14:59 ` [PATCH v12 4/9] timers: Use scoped_guard when setting/clearing the tmigr available flag Gabriele Monaco
2025-09-15 14:59 ` [PATCH v12 5/9] cgroup/cpuset: Rename update_unbound_workqueue_cpumask() to update_exclusion_cpumasks() Gabriele Monaco
2025-09-15 14:59 ` [PATCH v12 6/9] sched/isolation: Force housekeeping if isolcpus and nohz_full don't leave any Gabriele Monaco
2025-09-15 14:59 ` [PATCH v12 7/9] cgroup/cpuset: Fail if isolated and nohz_full don't leave any housekeeping Gabriele Monaco
2025-09-15 20:43   ` Waiman Long
2025-09-16  8:31   ` Chen Ridong
2025-09-15 14:59 ` [PATCH v12 8/9] cpumask: Add initialiser CPUMASK_NULL to use cleanup helpers Gabriele Monaco
2025-09-15 16:04   ` Yury Norov
2025-09-15 17:02     ` Gabriele Monaco
2025-09-15 18:35       ` Yury Norov
2025-09-16 11:27         ` Frederic Weisbecker [this message]
2025-09-17  7:51           ` Gabriele Monaco
2025-09-17 11:38             ` Yury Norov
2025-09-17 12:08               ` Gabriele Monaco
2025-09-17 12:34                 ` Yury Norov
2025-09-19 14:58                   ` Yury Norov
2025-09-22 10:07                     ` Gabriele Monaco
2025-09-15 14:59 ` [PATCH v12 9/9] timers: Exclude isolated cpus from timer migration Gabriele Monaco
2025-09-15 20:51   ` John B. Wyatt IV
2025-09-16  5:29     ` Gabriele Monaco
2025-09-16 13:41   ` Frederic Weisbecker

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=aMlJqDjWNyak07LX@localhost.localdomain \
    --to=frederic@kernel.org \
    --cc=gmonaco@redhat.com \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox