From: "Arnd Bergmann" <arnd@arndb.de>
To: "Chester Lin" <chester62515@gmail.com>, "Shawn Guo" <shawnguo2@yeah.net>
Cc: "Matthias Brugger" <mbrugger@suse.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Ghennadi Procopciuc" <ghennadi.procopciuc@oss.nxp.com>,
"Olof Johansson" <olof@lixom.net>,
krzysztof.kozlowski+dt@linaro.org,
"Andreas Färber" <afaerber@suse.de>,
"Rob Herring" <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, soc@kernel.org,
"NXP S32 Linux Team" <s32@nxp.com>,
"Ghennadi Procopciuc" <ghennadi.procopciuc@nxp.com>,
"Shawn Guo" <shawnguo@kernel.org>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"NXP Linux Team" <linux-imx@nxp.com>
Subject: Re: [PATCH 1/1] MAINTAINERS: Add maintainer for NXP S32G boards
Date: Sat, 24 Feb 2024 12:42:30 +0100 [thread overview]
Message-ID: <57dce440-d24b-4638-9395-62dfb03ec002@app.fastmail.com> (raw)
In-Reply-To: <ZdmZ4JC0CsX2qs5C@linux-8mug>
On Sat, Feb 24, 2024, at 08:25, Chester Lin wrote:
> Hi all,
>
> Sorry for the late reply since I lost connection with upstream due to a
> health condition, which affected my eyesights for a while so I tried to use
> my eyes as less as possible. Please accept my apologies anyway.
No worries, and thanks for the clarifications.
> On Fri, Feb 23, 2024 at 10:42:58PM +0800, Shawn Guo wrote:
>> On Fri, Feb 23, 2024 at 01:29:10PM +0100, Arnd Bergmann wrote:
>
> Before leaving SUSE I reached NXP to see if anyone could take over it but I
> didn't get response unfortunately. Maybe it was too rush to find a right person
> at the moment but I still wish that someone can take over this role based on the
> following reasons:
>
> - Since I have returned my S32G boards to SUSE, currently I do not have
> a platform
> to verify S32G patches unless I could get a new one. I wish I could
> still help
> out but hardware & doc resources will be the biggest challenge to me.
>
> - My current employee may have competitive relationship with NXP in automotive
> field, which means I may not be fit in this role unless nobody cares.
In general, there no problem to just retire from a maintainer
position or mark it as 'Odd fixes' instead of 'Maintained' when
you are no longer planning to actively maintain it.
>> >
>> > 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.
>>
>> It's unintentional that IMX entry covers s32 dts files, as they have a
>> dedicated entry.
>>
>> ARM/NXP S32G ARCHITECTURE
>> M: Chester Lin <chester62515@gmail.com>
>> R: Andreas Färber <afaerber@suse.de>
>> R: Matthias Brugger <mbrugger@suse.com>
>> R: NXP S32 Linux Team <s32@nxp.com>
>> L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
>> S: Maintained
>> F: arch/arm64/boot/dts/freescale/s32g*.dts*
>>
>> However I'm fine with collecting and sending patches through IMX tree,
>> if S32G folks help review them.
>>
>
> This looks good to me as well.
Ok, in this case I would suggest we change this section to
only have 'R:' entries and no 'M:' for the moment.
Between the four of you (Chester, Andreas, Matthias, Ghennadi),
I think we can choose to keep everyone or drop those that are
unlikely to actually review patches. Please let us know you
would like to be included as a reviewer or not.
For the pinctrl driver, I would add the files to the "freescale"
pinctrl entry in a similar way and end up with
diff --git a/MAINTAINERS b/MAINTAINERS
index efeaeb51f183..c1924c0053bc 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2555,13 +2555,14 @@ F: drivers/*/*/*wpcm*
F: drivers/*/*wpcm*
ARM/NXP S32G ARCHITECTURE
-M: Chester Lin <chester62515@gmail.com>
+R: Chester Lin <chester62515@gmail.com>
R: Andreas Färber <afaerber@suse.de>
R: Matthias Brugger <mbrugger@suse.com>
R: NXP S32 Linux Team <s32@nxp.com>
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
S: Maintained
F: arch/arm64/boot/dts/freescale/s32g*.dts*
+F: drivers/pinctrl/nxp/
ARM/Orion SoC/Technologic Systems TS-78xx platform support
M: Alexander Clouter <alex@digriz.org.uk>
@@ -17415,7 +17416,9 @@ R: Pengutronix Kernel Team <kernel@pengutronix.de>
L: linux-gpio@vger.kernel.org
S: Maintained
F: Documentation/devicetree/bindings/pinctrl/fsl,*
+F: Documentation/devicetree/bindings/pinctrl/nxp,s32*
F: drivers/pinctrl/freescale/
+F: drivers/pinctrl/nxp/
PIN CONTROLLER - INTEL
M: Mika Westerberg <mika.westerberg@linux.intel.com>
@@ -17469,14 +17472,6 @@ S: Supported
F: drivers/gpio/gpio-sama5d2-piobu.c
F: drivers/pinctrl/pinctrl-at91*
-PIN CONTROLLER - NXP S32
-M: Chester Lin <clin@suse.com>
-R: NXP S32 Linux Team <s32@nxp.com>
-L: linux-gpio@vger.kernel.org
-S: Maintained
-F: Documentation/devicetree/bindings/pinctrl/nxp,s32*
-F: drivers/pinctrl/nxp/
-
PIN CONTROLLER - QUALCOMM
M: Bjorn Andersson <andersson@kernel.org>
L: linux-arm-msm@vger.kernel.org
next prev parent reply other threads:[~2024-02-24 11:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 12:01 [PATCH 0/1] MAINTAINERS: Add S32G SoC maintainer Ghennadi Procopciuc
2024-02-21 12:01 ` [PATCH 1/1] MAINTAINERS: Add maintainer for NXP S32G boards Ghennadi Procopciuc
2024-02-21 14:42 ` Krzysztof Kozlowski
2024-02-21 14:45 ` Krzysztof Kozlowski
2024-02-21 15:19 ` Ghennadi Procopciuc
2024-02-21 15:43 ` Krzysztof Kozlowski
2024-02-21 17:00 ` Ghennadi Procopciuc
2024-02-22 11:13 ` Krzysztof Kozlowski
2024-02-23 12:02 ` Matthias Brugger
2024-02-23 12:29 ` Arnd Bergmann
2024-02-23 14:42 ` Shawn Guo
2024-02-24 7:25 ` Chester Lin
2024-02-24 7:56 ` Chester Lin
2024-02-24 11:42 ` Arnd Bergmann [this message]
2024-02-26 7:33 ` Ghennadi Procopciuc
2024-02-26 9:55 ` Matthias Brugger
2024-02-28 15:19 ` Matthias Brugger
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=57dce440-d24b-4638-9395-62dfb03ec002@app.fastmail.com \
--to=arnd@arndb.de \
--cc=afaerber@suse.de \
--cc=chester62515@gmail.com \
--cc=festevam@gmail.com \
--cc=ghennadi.procopciuc@nxp.com \
--cc=ghennadi.procopciuc@oss.nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbrugger@suse.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=s32@nxp.com \
--cc=shawnguo2@yeah.net \
--cc=shawnguo@kernel.org \
--cc=soc@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
all inboxes | Powered by JetHome®