linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo2@yeah.net>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Matthias Brugger" <mbrugger@suse.com>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	"Ghennadi Procopciuc" <ghennadi.procopciuc@oss.nxp.com>,
	"Olof Johansson" <olof@lixom.net>,
	"Chester Lin" <chester62515@gmail.com>,
	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: Fri, 23 Feb 2024 22:42:58 +0800	[thread overview]
Message-ID: <Zdiu8s5Cgz9s6dLP@dragon> (raw)
In-Reply-To: <c3e68c62-b81f-475b-9b15-c983c94aed8b@app.fastmail.com>

On Fri, Feb 23, 2024 at 01:29:10PM +0100, Arnd Bergmann wrote:
> 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@kernel.org>
> M:      Sascha Hauer <s.hauer@pengutronix.de>
> R:      Pengutronix Kernel Team <kernel@pengutronix.de>
> R:      Fabio Estevam <festevam@gmail.com>
> R:      NXP Linux Team <linux-imx@nxp.com> 
> L:      linux-arm-kernel@lists.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.

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.

Shawn


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-02-23 14:43 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 [this message]
2024-02-24  7:25                     ` Chester Lin
2024-02-24  7:56                       ` Chester Lin
2024-02-24 11:42                       ` Arnd Bergmann
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=Zdiu8s5Cgz9s6dLP@dragon \
    --to=shawnguo2@yeah.net \
    --cc=afaerber@suse.de \
    --cc=arnd@arndb.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=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;
as well as URLs for NNTP newsgroup(s).