[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e538ded0-bd3a-4ca4-b2bd-8d20d8c8c3fe@linaro.org>
Date: Wed, 21 Feb 2024 16:43:13 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Ghennadi Procopciuc <ghennadi.procopciuc@....nxp.com>,
Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
Chester Lin <chester62515@...il.com>, krzysztof.kozlowski+dt@...aro.org,
Andreas Färber <afaerber@...e.de>,
Matthias Brugger <mbrugger@...e.com>, 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>
Subject: Re: [PATCH 1/1] MAINTAINERS: Add maintainer for NXP S32G boards
On 21/02/2024 16:19, Ghennadi Procopciuc wrote:
> On 2/21/24 16:45, Krzysztof Kozlowski wrote:
>> On 21/02/2024 15:42, Krzysztof Kozlowski wrote:
>>> On 21/02/2024 13:01, Ghennadi Procopciuc wrote:
>>>> From: Ghennadi Procopciuc <ghennadi.procopciuc@....com>
>>>>
>>>> Add myself as a maintainer of the NXP S32G DT files.
>>>
>>> No need for cover letters for single patches. OTOH, this commit msg is
>>> empty...
> Thank you, I can correct that.
>
>>> Plus your patch looks corrupted (wrong encoding): F??rber
>
> Indeed, it is due to 'Content-Type: text/plain; charset="us-ascii"'.
> I can fix this as part of v2.
>
>>> BTW, did you contribute anything to the upstream Linux kernel? Do you
>>> know the process? Downstream does not really matter.
>>
>> I found the answer:
>>
>> From: Ghennadi Procopciuc <ghennadi.procopciuc@....com>
>> Signed-off-by: Ghennadi Procopciuc <ghennadi.procopciuc@....nxp.com>
>>
>> Does not look like. Please get some upstream work experience first.
>>
>> https://lore.kernel.org/all/?q=f%3Aghennadi.procopciuc%40oss.nxp.com
>
> Although I am new to upstream communities and may make mistakes, I am
> eager to learn and improve.
>
> After leaving SuSe[0], the current maintainer of the NXP S32G DT files
> became inactive[1]. As a result, this area is not currently being
> maintained. This is the actual reason why I attempted to add myself as a
> maintainer of that area. Although I acknowledge that I may not have
> enough experience to become a maintainer, I am concerned that the NXP
> S32G DT patch submission may be blocked for everyone due to the current
> situation.
I would be just happy to see first actual contributions or any sort of
activity, like reviewing, before taking over something.
You do not need to become maintainer to provide reviews. By reviewing
patches you already reduce burden/work from the maintainers.
Best regards,
Krzysztof
Powered by blists - more mailing lists