lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e9d061fb-c377-46a8-bd01-e661a75122a5@oss.nxp.com>
Date: Mon, 26 Feb 2024 09:33:44 +0200
From: Ghennadi Procopciuc <ghennadi.procopciuc@....nxp.com>
To: Arnd Bergmann <arnd@...db.de>, Chester Lin <chester62515@...il.com>,
 Shawn Guo <shawnguo2@...h.net>
Cc: Matthias Brugger <mbrugger@...e.com>,
 Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
 Olof Johansson <olof@...om.net>, krzysztof.kozlowski+dt@...aro.org,
 Andreas Färber <afaerber@...e.de>,
 Rob Herring <robh+dt@...nel.org>, 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 2/24/24 13:42, Arnd Bergmann wrote:
> 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@...il.com>
>>> R:      Andreas Färber <afaerber@...e.de>
>>> R:      Matthias Brugger <mbrugger@...e.com>
>>> R:      NXP S32 Linux Team <s32@....com>
>>> L:      linux-arm-kernel@...ts.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.

I agree, this looks good to me too.

> 
> 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.

I would like to be included as reviewer.
Can we add Shawn as the maintainer since Chester agreed to pass on the
responsibility to him?

> 
> 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@...il.com>
> +R:     Chester Lin <chester62515@...il.com>
>  R:     Andreas Färber <afaerber@...e.de>
>  R:     Matthias Brugger <mbrugger@...e.com>
>  R:     NXP S32 Linux Team <s32@....com>
>  L:     linux-arm-kernel@...ts.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@...riz.org.uk>
> @@ -17415,7 +17416,9 @@ R:      Pengutronix Kernel Team <kernel@...gutronix.de>
>  L:     linux-gpio@...r.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/

Could you please add 'L: NXP S32 Linux Team <s32@....com>', given that
this list is relevant for S32 patches ?

>  PIN CONTROLLER - INTEL
>  M:     Mika Westerberg <mika.westerberg@...ux.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@...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/
> -
>  PIN CONTROLLER - QUALCOMM
>  M:     Bjorn Andersson <andersson@...nel.org>
>  L:     linux-arm-msm@...r.kernel.org

Best regards,
Ghennadi


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ