From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, yury.norov@gmail.com,
linux-perf-users@vger.kernel.org, mingo@kernel.org,
juri.lelli@redhat.com, vincent.guittot@linaro.org,
tglx@kernel.org, sudeep.holla@kernel.org,
linux@rasmusvillemoes.dk
Subject: Re: [PATCH 0/5] cpumask: Use cpumask_intersects* APIs where applicable
Date: Thu, 12 Nov 2026 12:39:43 +0530 [thread overview]
Message-ID: <2c0599b0-4f3c-41f8-b87f-ce43dd289b9d@linux.ibm.com> (raw)
In-Reply-To: <20261111101013.GH2668564@noisy.programming.kicks-ass.net>
On 11/11/26 3:40 PM, Peter Zijlstra wrote:
> On Wed, Nov 11, 2026 at 02:52:58PM +0530, Shrikanth Hegde wrote:
>>
>>
>> On 11/11/26 2:46 PM, Peter Zijlstra wrote:
>>> On Wed, Nov 11, 2026 at 01:29:40PM +0530, Shrikanth Hegde wrote:
>>>
>>>> Shrikanth Hegde (5):
>>>
>>>> cpuidle: Use cpumask_intersects_and where applicable
>>>> arch_topology: Use cpumask_intersects where applicable
>>>> drivers/base/arch_topology.c | 9 +--------
>>>> drivers/cpuidle/coupled.c | 4 ++--
>>>
>>> That's not actually code I maintain. That's rjw stuff.
>>
>> Yes. Sorry, I should have cc'ed him.
>>
>> Should I split this series and send it to each subsystem instead?
>
> I've taken the first 3 patches since that's all tip stuff.
Thanks Peter.
> Feel free to
> resend the last two with appropriate Ccs. Its all independent patches
> anyway.
Rafael or greg may not have got a chance to see it.
I will wait for few days if the last two can be picked up from this series.
If not, Then I will resend last two as independent patches.
next prev parent reply other threads:[~2026-11-12 7:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 7:59 [PATCH 0/5] cpumask: Use cpumask_intersects* APIs where applicable Shrikanth Hegde
2026-11-11 7:59 ` [PATCH 1/5] sched/rt: cpupri_find: Use cpumask_intersects " Shrikanth Hegde
2026-11-11 8:06 ` sashiko-bot
2026-11-11 7:59 ` [PATCH 2/5] cpu/hotplug: " Shrikanth Hegde
2026-11-11 8:09 ` sashiko-bot
2026-11-11 7:59 ` [PATCH 3/5] perf: " Shrikanth Hegde
2026-11-11 8:20 ` sashiko-bot
2026-11-11 7:59 ` [PATCH 4/5] cpuidle: Use cpumask_intersects_and " Shrikanth Hegde
2026-11-11 8:03 ` sashiko-bot
2026-11-11 7:59 ` [PATCH 5/5] arch_topology: Use cpumask_intersects " Shrikanth Hegde
2026-11-11 8:03 ` sashiko-bot
2026-11-11 10:20 ` Sudeep Holla
2026-11-11 9:16 ` [PATCH 0/5] cpumask: Use cpumask_intersects* APIs " Peter Zijlstra
2026-11-11 9:22 ` Shrikanth Hegde
2026-11-11 10:10 ` Peter Zijlstra
2026-11-12 7:09 ` Shrikanth Hegde [this message]
2026-11-11 16:38 ` Yury Norov
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=2c0599b0-4f3c-41f8-b87f-ce43dd289b9d@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=sudeep.holla@kernel.org \
--cc=tglx@kernel.org \
--cc=vincent.guittot@linaro.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