From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: maddy@linux.ibm.com, chleroy@kernel.org
Cc: linux-kernel@vger.kernel.org, linux@rasmusvillemoes.dk,
linuxppc-dev@lists.ozlabs.org, yury.norov@gmail.com
Subject: Re: [PATCH v2 0/4] powerpc: A few misc cpumask changes
Date: Mon, 18 May 2026 10:14:02 +0530 [thread overview]
Message-ID: <0233138b-57bb-4cdf-86b9-8a48fa8b54c3@linux.ibm.com> (raw)
In-Reply-To: <20260427044715.559137-1-sshegde@linux.ibm.com>
Hi Maddy, Christophe,
> Based on tip/master at: (dffc5753ba4c "Merge branch into tip/master: 'timers/clocksource'")
>
Gentle Ping,
Still applies cleanly to today's tip master.
> Shrikanth Hegde (4):
> powerpc: Use cpumask_next_wrap instead
> powerpc: Simplify cpumask api usage for cpuinfo display
> powerpc/perf: Use cpumask_intersects api for checking disable path
> powerpc/xive: Add warning if target CPU not found
>
> arch/powerpc/kernel/irq.c | 5 +----
> arch/powerpc/kernel/setup-common.c | 7 ++-----
> arch/powerpc/mm/book3s64/hash_utils.c | 4 +---
> arch/powerpc/perf/imc-pmu.c | 6 ++----
> arch/powerpc/sysdev/xive/common.c | 1 +
> 5 files changed, 7 insertions(+), 16 deletions(-)
>
Do you have any comments on this? Do you want me to resend with yury's tag?
prev parent reply other threads:[~2026-05-18 4:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 4:47 [PATCH v2 0/4] powerpc: A few misc cpumask changes Shrikanth Hegde
2026-04-27 4:47 ` [PATCH v2 1/4] powerpc: Use cpumask_next_wrap instead Shrikanth Hegde
2026-04-27 4:47 ` [PATCH v2 2/4] powerpc: Simplify cpumask api usage for cpuinfo display Shrikanth Hegde
2026-04-27 4:47 ` [PATCH v2 3/4] powerpc/perf: Use cpumask_intersects api for checking disable path Shrikanth Hegde
2026-04-27 4:47 ` [PATCH v2 4/4] powerpc/xive: Add warning if target CPU not found Shrikanth Hegde
2026-04-28 16:41 ` [PATCH v2 0/4] powerpc: A few misc cpumask changes Yury Norov
2026-05-18 4:44 ` Shrikanth Hegde [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=0233138b-57bb-4cdf-86b9-8a48fa8b54c3@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=chleroy@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--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