From: Thomas Gleixner <tglx@linutronix.de>
To: Nam Cao <namcao@linutronix.de>, Marc Zyngier <maz@kernel.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: Nam Cao <namcao@linutronix.de>
Subject: Re: [PATCH 0/3] powerpc: Cleanup and convert to MSI parent domain
Date: Thu, 03 Jul 2025 18:37:19 +0200 [thread overview]
Message-ID: <87sejdtem8.ffs@tglx> (raw)
In-Reply-To: <cover.1750861319.git.namcao@linutronix.de>
On Thu, Jun 26 2025 at 16:47, Nam Cao wrote:
> The solution is implementing per device MSI domains, this means the
> entities which provide global PCI/MSI domain so far have to implement MSI
> parent domain functionality instead.
>
> This series:
>
> - Untangle XIVE driver from Powernv and Pseries drivers
>
> - Convert the Powernv and Pseries drivers to implement MSI parent domain
> functionality
>
> Nam Cao (3):
> powerpc/xive: Untangle xive from child interrupt controller drivers
> powerpc/powernv/pci: Switch to use msi_create_parent_irq_domain()
> powerpc/pseries/msi: Switch to msi_create_parent_irq_domain()
Gentle reminder @PPC people.
Thanks,
tglx
next prev parent reply other threads:[~2025-07-03 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 14:47 [PATCH 0/3] powerpc: Cleanup and convert to MSI parent domain Nam Cao
2025-06-26 14:47 ` [PATCH 1/3] powerpc/xive: Untangle xive from child interrupt controller drivers Nam Cao
2025-06-26 14:47 ` [PATCH 2/3] powerpc/powernv/pci: Switch to use msi_create_parent_irq_domain() Nam Cao
2025-06-26 14:47 ` [PATCH 3/3] powerpc/pseries/msi: Switch to msi_create_parent_irq_domain() Nam Cao
2025-07-03 16:37 ` Thomas Gleixner [this message]
2025-07-22 8:35 ` [PATCH 0/3] powerpc: Cleanup and convert to MSI parent domain Gautam Menghani
2025-07-22 9:24 ` Nam Cao
2025-07-22 20:31 ` Nam Cao
2025-07-23 10:57 ` Gautam Menghani
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=87sejdtem8.ffs@tglx \
--to=tglx@linutronix.de \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=maz@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=namcao@linutronix.de \
--cc=npiggin@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;
as well as URLs for NNTP newsgroup(s).