From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E9BAC371045 for ; Mon, 18 May 2026 13:51:52 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779112313; cv=none; b=kVY+xEOPVENE2235D6Lo3qx78edVUvpZyyhG1YkvLXbur0k4VLVriq8sqUpOVKI2xzxgX1cSQf07ftA5vVYh1wIVhSSQ2vlCtLM4SVvtAvcLMlHN5jbw1NgI18ffLgzl2Q/f/jyqk6L2gmIMAZ1+RmQGfa9FpRfJheRyAtN0H/o= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779112313; c=relaxed/simple; bh=tTiSLoD171HOH9MG6UW2Ctw5fFKZ7i03l/tZXd81gA0=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=posXaE399Zp/KyMyOHPi18CjD1CdoK2zTMCAmTePVR54mcB5sSMESstM2F2GJFpeO3kAh546WdbKCfNkODxOaKaVJ5ZHwTuzuiSDqKl9rmSDXHm3TqXp912NRjwGxho5ohfOCvV3o98faWQzjBgkLR2U2PqZlj+QRfK0Jy7ZVA4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=KpVPMYOO; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="KpVPMYOO" Received: by smtp.kernel.org (Postfix) with ESMTPSA id D33A4C2BCB8; Mon, 18 May 2026 13:51:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1779112312; bh=tTiSLoD171HOH9MG6UW2Ctw5fFKZ7i03l/tZXd81gA0=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=KpVPMYOOQGSZUQyavZov1lTId0F2PnFZ5ubdKezcRZizgMLp0LPs1hklw+3/6K6LW 7BNdCNjZ1mYNLUPSPgPNP0Kes1UGCcZ/h2BAJ9TGgoNw73xdnoah1kb3Jh56JGcyro eRh+o9IjS+j2TPCyxxpoBj8dVwYJLs/Wl7Yfdck1392G0aYpOkzoZw8UJSDqIr3Ww1 ii9ahi96yMY8BRaky6Ib59I5LV+mWCZh006nV+Pn6H3USUdbpHqYBYOUbctJZmhhXL SvB/q2UZPZR/oq/nacuYEZe7tLh88cVtmTGnDdT3PlmeeUG8YLpkyxzx1iXyrB549K NvIWXAwBsbpEg== Message-ID: <4f34dc22-8dd7-42fb-8c16-4e359faf60d6@kernel.org> Date: Mon, 18 May 2026 15:51:48 +0200 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v2 0/6] fsl-mc: Move over to device MSI infrastructure To: Marc Zyngier , Arnd Bergmann Cc: Ioana Ciornei , Thomas Gleixner , Sascha Bischoff , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linuxppc-dev@lists.ozlabs.org References: <20260224100936.3752303-1-maz@kernel.org> <177209938125.547814.7154250802402503122.b4-ty@kernel.org> <87v7cva080.wl-maz@kernel.org> Content-Language: fr-FR From: "Christophe Leroy (CS GROUP)" In-Reply-To: <87v7cva080.wl-maz@kernel.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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)" 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/