From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Marc Zyngier <maz@kernel.org>, Arnd Bergmann <arnd@kernel.org>
Cc: Ioana Ciornei <ioana.ciornei@nxp.com>,
Thomas Gleixner <tglx@kernel.org>,
Sascha Bischoff <sascha.bischoff@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 0/6] fsl-mc: Move over to device MSI infrastructure
Date: Mon, 18 May 2026 15:51:48 +0200 [thread overview]
Message-ID: <4f34dc22-8dd7-42fb-8c16-4e359faf60d6@kernel.org> (raw)
In-Reply-To: <87v7cva080.wl-maz@kernel.org>
Hi Marc,
Le 10/05/2026 à 15:00, Marc Zyngier a écrit :
> On Thu, 26 Feb 2026 09:50:43 +0000,
> "Christophe Leroy (CS GROUP)" <chleroy@kernel.org> wrote:
>>
>>
>> On Tue, 24 Feb 2026 10:09:30 +0000, Marc Zyngier wrote:
>>> This is the second drop of this cleanup series for the fsl-mc MSI
>>> infrastructure, initially posted at [1].
>>>
>>> * From v1 [1]:
>>>
>>> - Drop the now unused DOMAIN_BUS_FSL_MC_MSI bus token
>>>
>>> [...]
>>
>> Applied, thanks!
>>
>> [1/6] fsl-mc: Remove MSI domain propagation to sub-devices
>> commit: 1fb7392ee3408494d4d62c09a8c3e5f5934caba7
>> [2/6] fsl-mc: Add minimal infrastructure to use platform MSI
>> commit: 0c9f522f2d41c7e055a602a0d2c41dc7af01010b
>> [3/6] irqchip/gic-v3-its: Add fsl_mc device plumbing to the msi-parent handling
>> commit: cf3179b4e53f527aba9f0c6c3b921619c8adf761
>> [4/6] fsl-mc: Switch over to per-device platform MSI
>> commit: 4a958e47c246fa3fb8954f4303e0da15ab3d026d
>> [5/6] fsl-mc: Remove legacy MSI implementation
>> commit: 14b1cbcc6cec0b02298f4adf717646cd943b7ef6
>> [6/6] platform-msi: Remove stale comment
>> commit: f0a2eac6a597268034fd40d92c1469182438b53d
>
> Is there any particular reason why this didn't make it into 7.1?
I sent a pull request [1] as early as possible after Easter break, but
it was apparently too late. Or maybe that was because I did a last
minute rebase, I'm not sure what the real reason. I tentatively sent an
alternative pull request [2] the day after after rolling back the
rebase, but I got no feedback.
>
> I was really looking forward to some additional cleanups in the GICv3
> ITS code, and this gets in the way.
It is still in linux-next and finger crossed will go in 7.2
> > Do I need to respin it?
No, I'd like to avoid having to rebase again. If you have changes to the
series please send followup patches.
Christophe
[1]
https://patchwork.kernel.org/project/linux-soc/patch/69cdadd6-523c-4a79-8cb3-1deff5910699@kernel.org/
[2]
https://patchwork.kernel.org/project/linux-soc/patch/310b65ba-1d73-4ce0-b332-00cde70acc69@kernel.org/
next prev parent reply other threads:[~2026-05-18 13:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 10:09 [PATCH v2 0/6] fsl-mc: Move over to device MSI infrastructure Marc Zyngier
2026-02-24 10:09 ` [PATCH v2 1/6] fsl-mc: Remove MSI domain propagation to sub-devices Marc Zyngier
2026-02-24 10:09 ` [PATCH v2 2/6] fsl-mc: Add minimal infrastructure to use platform MSI Marc Zyngier
2026-02-24 10:09 ` [PATCH v2 3/6] irqchip/gic-v3-its: Add fsl_mc device plumbing to the msi-parent handling Marc Zyngier
2026-02-24 10:09 ` [PATCH v2 4/6] fsl-mc: Switch over to per-device platform MSI Marc Zyngier
2026-02-24 10:09 ` [PATCH v2 5/6] fsl-mc: Remove legacy MSI implementation Marc Zyngier
2026-02-24 10:09 ` [PATCH v2 6/6] platform-msi: Remove stale comment Marc Zyngier
2026-02-24 16:15 ` [PATCH v2 0/6] fsl-mc: Move over to device MSI infrastructure Thomas Gleixner
2026-02-26 9:50 ` Christophe Leroy (CS GROUP)
2026-05-10 13:00 ` Marc Zyngier
2026-05-18 13:51 ` Christophe Leroy (CS GROUP) [this message]
2026-05-18 14:24 ` Marc Zyngier
2026-05-18 15:24 ` Arnd Bergmann
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=4f34dc22-8dd7-42fb-8c16-4e359faf60d6@kernel.org \
--to=chleroy@kernel.org \
--cc=arnd@kernel.org \
--cc=ioana.ciornei@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maz@kernel.org \
--cc=sascha.bischoff@arm.com \
--cc=tglx@kernel.org \
/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