public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: maddy@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
	yury.norov@gmail.com, linux@rasmusvillemoes.dk,
	linux-kernel@vger.kernel.org
Cc: sshegde@linux.ibm.com, chleroy@kernel.org
Subject: [PATCH 0/2] powerpc: A few misc cpumask refactors
Date: Fri, 27 Mar 2026 12:01:27 +0530	[thread overview]
Message-ID: <20260327063129.127302-1-sshegde@linux.ibm.com> (raw)

While going through the code, spotted these cpumask miscellaneous
changes. These are pure code refactors, they dont affect functionality
or performance. They just use the updated cpumask api and remove some
checks which are not necessary now.

Major one being:
cpu = cpumask_next(cpu, mask)
if (cpu >= nr_cpu_ids)
    cpu = cpumask_first(mask)
Above block can be replaced by cpu = cpumask_next_wrap(cpu, mask)


Note that exact same blocks are still present in:
arch/x86/kernel/tsc_sync.c
drivers/char/random.c
drivers/net/wireguard/queueing.h
drivers/net/ethernet/freescale/dpaa2/dpaa2-eth.c
drivers/net/ethernet/sfc/siena/efx_channels.c
drivers/net/ethernet/sfc/efx_channels.c
kernel/rcu/rcutorture.c

Yury, Rasmus,
Do you think it makes sense to send for the above files too?

Shrikanth Hegde (2):
  powerpc: Use cpumask_next_wrap instead
  powerpc: Few misc cpumask code refactors

 arch/powerpc/kernel/irq.c             |  5 +----
 arch/powerpc/kernel/setup-common.c    |  7 ++-----
 arch/powerpc/mm/book3s64/hash_utils.c |  4 +---
 arch/powerpc/sysdev/xive/common.c     | 12 ++++--------
 4 files changed, 8 insertions(+), 20 deletions(-)

-- 
2.47.3



             reply	other threads:[~2026-03-27  6:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-27  6:31 Shrikanth Hegde [this message]
2026-03-27  6:31 ` [PATCH 1/2] powerpc: Use cpumask_next_wrap instead Shrikanth Hegde
2026-03-28 20:44   ` Yury Norov
2026-03-29  9:18     ` Shrikanth Hegde
2026-03-27  6:31 ` [PATCH 2/2] powerpc: Few misc cpumask code refactors Shrikanth Hegde
2026-03-28 20:27   ` 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=20260327063129.127302-1-sshegde@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