[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <c3e68c62-b81f-475b-9b15-c983c94aed8b@app.fastmail.com>
Date: Fri, 23 Feb 2024 13:29:10 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "Matthias Brugger" <mbrugger@...e.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@...aro.org>,
"Ghennadi Procopciuc" <ghennadi.procopciuc@....nxp.com>,
"Olof Johansson" <olof@...om.net>, "Chester Lin" <chester62515@...il.com>,
krzysztof.kozlowski+dt@...aro.org,
Andreas Färber <afaerber@...e.de>,
"Rob Herring" <robh+dt@...nel.org>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
soc@...nel.org, "NXP S32 Linux Team" <s32@....com>,
"Ghennadi Procopciuc" <ghennadi.procopciuc@....com>,
"Shawn Guo" <shawnguo@...nel.org>,
"Pengutronix Kernel Team" <kernel@...gutronix.de>,
"Sascha Hauer" <s.hauer@...gutronix.de>,
"Fabio Estevam" <festevam@...il.com>, "NXP Linux Team" <linux-imx@....com>
Subject: Re: [PATCH 1/1] MAINTAINERS: Add maintainer for NXP S32G boards
On Fri, Feb 23, 2024, at 13:02, Matthias Brugger wrote:
> On 22/02/2024 12:13, Krzysztof Kozlowski wrote:
>> On 21/02/2024 18:00, Ghennadi Procopciuc wrote:
>>
>> Andreas or Matthias,
>> Maybe you could change your R: into M: and take s32g patches?
>>
>> If not, then I will ack this patch making Ghennadi the maintainer.
>>
>
> Normal process would be that Arnd would contact Chester to see if he is
> not able
> to do the maintainer work any more. In that case maybe Arnd could take
> over.
I was hoping to see a reply from Chester one way or another,
I see he has been on Cc for the entire thread but not
chimed in.
> I'm not saying that Ghennadi won't be able to defend this, if it ever occurs.
> Basically because I don't have a good track record of him due to missing
> upstream collaboration.
>
> I would prefer that Arnd (or Andreas) step up to take the maintainer role. I
> already have one and it's difficult for me to find the time to do it in an
> acceptable way.
It appears that we already cover the dts files in the IMX
entry, whether that is intentional or not:
ARM/FREESCALE IMX / MXC ARM ARCHITECTURE
M: Shawn Guo <shawnguo@...nel.org>
M: Sascha Hauer <s.hauer@...gutronix.de>
R: Pengutronix Kernel Team <kernel@...gutronix.de>
R: Fabio Estevam <festevam@...il.com>
R: NXP Linux Team <linux-imx@....com>
L: linux-arm-kernel@...ts.infradead.org (moderated for non-subscribers)
S: Maintained
T: git git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git
F: arch/arm/boot/dts/nxp/imx/
F: arch/arm/boot/dts/nxp/mxs/
F: arch/arm64/boot/dts/freescale/
Added everyone there to Cc, having any s32 patches go through
the imx tree would be the easiest way as far as I'm concerned.
I've added the maintainers to Cc, let's see what they think.
I also noticed that the pinctrl driver entry still has Chester's
old email address listed as the only maintainer, so we should
probably fix that as well:
PIN CONTROLLER - NXP S32
M: Chester Lin <clin@...e.com>
R: NXP S32 Linux Team <s32@....com>
L: linux-gpio@...r.kernel.org
S: Maintained
F: Documentation/devicetree/bindings/pinctrl/nxp,s32*
F: drivers/pinctrl/nxp/
Arnd
Powered by blists - more mailing lists