From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, yury.norov@gmail.com,
linux@rasmusvillemoes.dk, linux-kernel@vger.kernel.org,
Shrikanth Hegde <sshegde@linux.ibm.com>
Cc: chleroy@kernel.org
Subject: Re: [PATCH v2 0/4] powerpc: A few misc cpumask changes
Date: Sat, 20 Jun 2026 03:29:59 +0530 [thread overview]
Message-ID: <178190618790.653308.14148704801994865382.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <20260427044715.559137-1-sshegde@linux.ibm.com>
On Mon, 27 Apr 2026 10:17:11 +0530, Shrikanth Hegde wrote:
> These are some miscellaneous code refactors around using cpumask
> APIs. They are mainly aimed at code simplification.
>
> Changes since v1:
> - Dropped the changes done in xive_find_target_in_mask. Those changes are
> done by Yury Norov already.
> - Collected the tags. Thanks to Yury Norov.
> - Added new patch to use cpumask_intersects instead of using
> temp_mask to achieve the same goal.
> - Added new patch to print the warning when target CPU not found
> as discussed in [2]. This patch is kept separate since this adds
> a new warning in case of failure. So one may perceive it as functional
> change.
>
> [...]
Applied to powerpc/next.
[1/4] powerpc: Use cpumask_next_wrap instead
https://git.kernel.org/powerpc/c/1ca0c82bbc72e8e3de0a41e6dbf92473c00f3d1e
[2/4] powerpc: Simplify cpumask api usage for cpuinfo display
https://git.kernel.org/powerpc/c/a66eab7a5d7decadad51b4204c6f2f0d8cf665d1
[3/4] powerpc/perf: Use cpumask_intersects api for checking disable path
https://git.kernel.org/powerpc/c/1f8986fdae91880411a3be907879ba63973da100
[4/4] powerpc/xive: Add warning if target CPU not found
https://git.kernel.org/powerpc/c/0521dbbc5710aca3b3d189747781761732289623
cheers
prev parent reply other threads:[~2026-06-19 22:00 UTC|newest]
Thread overview: 8+ 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
2026-06-19 21:59 ` Madhavan Srinivasan [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=178190618790.653308.14148704801994865382.b4-ty@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=chleroy@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sshegde@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