From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
Thomas Gleixner <tglx@kernel.org>, Nam Cao <namcao@linutronix.de>,
"Jiri Slaby (SUSE)" <jirislaby@kernel.org>,
Kees Cook <kees@kernel.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Yury Norov <ynorov@nvidia.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 0/2] powerpc/xive: rework xive_find_target_in_mask()
Date: Wed, 8 Apr 2026 09:59:15 +0530 [thread overview]
Message-ID: <177562236420.1381144.8638668034024786193.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <20260319033647.881246-1-ynorov@nvidia.com>
On Wed, 18 Mar 2026 23:36:44 -0400, Yury Norov wrote:
> Simplify the function by switching to using a modern cpumask API.
>
> Yury Norov (2):
> Revert "powerpc/xive: Fix the size of the cpumask used in
> xive_find_target_in_mask()"
> powerpc/xive: rework xive_find_target_in_mask()
>
> [...]
Applied to powerpc/next.
[1/2] Revert "powerpc/xive: Fix the size of the cpumask used in xive_find_target_in_mask()"
https://git.kernel.org/powerpc/c/cad2a72c29e037f1ade0079f7e4b925508680e20
[2/2] powerpc/xive: rework xive_find_target_in_mask()
https://git.kernel.org/powerpc/c/ce7c43b0871989b4c665cceb9720d79b933c1818
cheers
prev parent reply other threads:[~2026-04-08 4:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 3:36 [PATCH 0/2] powerpc/xive: rework xive_find_target_in_mask() Yury Norov
2026-03-19 3:36 ` [PATCH 1/2] Revert "powerpc/xive: Fix the size of the cpumask used in xive_find_target_in_mask()" Yury Norov
2026-03-20 5:57 ` Mukesh Kumar Chaurasiya
2026-03-19 3:36 ` [PATCH 2/2] powerpc/xive: rework xive_find_target_in_mask() Yury Norov
2026-03-29 9:13 ` Shrikanth Hegde
2026-03-30 17:04 ` Yury Norov
2026-03-31 2:59 ` Shrikanth Hegde
2026-03-31 5:30 ` Madhavan Srinivasan
2026-03-20 6:01 ` [PATCH 0/2] " Mukesh Kumar Chaurasiya
2026-04-08 4:29 ` 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=177562236420.1381144.8638668034024786193.b4-ty@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=chleroy@kernel.org \
--cc=jirislaby@kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=namcao@linutronix.de \
--cc=npiggin@gmail.com \
--cc=tglx@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=ynorov@nvidia.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