From: Krzysztof Kozlowski <krzk@kernel.org>
To: Andrei Stefanescu <andrei.stefanescu@oss.nxp.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Chester Lin <chester62515@gmail.com>,
Matthias Brugger <mbrugger@suse.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
NXP S32 Linux Team <s32@nxp.com>
Subject: Re: [PATCH v2 4/4] MAINTAINERS: add MAINTAINER for S32G2 SIUL2 GPIO driver
Date: Wed, 18 Sep 2024 10:13:23 +0200 [thread overview]
Message-ID: <e9449091-bd99-46ea-9f76-bbe0ce646c5d@kernel.org> (raw)
In-Reply-To: <53bae020-3d82-4966-8a51-2b3853d07eb8@oss.nxp.com>
On 18/09/2024 09:57, Andrei Stefanescu wrote:
> Hi Krzysztof,
>
> On 17/09/2024 20:44, Krzysztof Kozlowski wrote:
>> On 13/09/2024 10:29, Andrei Stefanescu wrote:
>>> Signed-off-by: Andrei Stefanescu <andrei.stefanescu@oss.nxp.com>
>>> ---
>>> MAINTAINERS | 2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index 10430778c998..e23c4369b6e1 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -2689,10 +2689,12 @@ ARM/NXP S32G ARCHITECTURE
>>> R: Chester Lin <chester62515@gmail.com>
>>> R: Matthias Brugger <mbrugger@suse.com>
>>> R: Ghennadi Procopciuc <ghennadi.procopciuc@oss.nxp.com>
>>> +R: Andrei Stefanescu <andrei.stefanescu@oss.nxp.com>
>>
>> That's another patch where NXP adds silently themself as platform
>> maintainer without explanation. Although here at least existing
>> maintainers are Cced.
>>
>> This looks like some pattern, so maybe clarifications are needed.
>>
>> You wanted to be maintainer of this driver alone, right? So separate entry.
>
> I would actually want to become a maintainer for the platform. I have
> already added changes to the pinctrl driver and the s32g2.dtsi/s32g3.dtsi files.
> I intend to submit more patches to these files and I would like to review
> changes to them.
That's fine, so please provide some sort of message in the commit,
describing your intention, document the commitment.
>
> However, if you or any of the existing maintainers consider that I should
> only add myself as a maintainer for the SIUL2 GPIO driver, I can fix this in v3.
I assume you proposed this after consulting them? It is unusual to add
yourself to maintainers without first talking to existing folks...
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-18 8:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 8:29 [PATCH v2 0/4] gpio: siul2-s32g2: add initial GPIO driver Andrei Stefanescu
2024-09-13 8:29 ` [PATCH v2 1/4] drivers: provide devm_platform_get_and_ioremap_resource_byname() Andrei Stefanescu
2024-09-18 7:52 ` Matthias Brugger
2024-09-13 8:29 ` [PATCH v2 2/4] dt-bindings: gpio: add support for NXP S32G2/S32G3 SoCs Andrei Stefanescu
2024-09-13 9:35 ` Rob Herring (Arm)
2024-09-13 9:55 ` Andrei Stefanescu
2024-09-13 14:13 ` Rob Herring
2024-09-16 6:01 ` Andrei Stefanescu
2024-09-13 8:29 ` [PATCH v2 3/4] gpio: siul2-s32g2: add NXP S32G2/S32G3 SoCs support Andrei Stefanescu
2024-09-14 16:40 ` Markus Elfring
2024-09-16 8:14 ` Andrei Stefanescu
2024-09-13 8:29 ` [PATCH v2 4/4] MAINTAINERS: add MAINTAINER for S32G2 SIUL2 GPIO driver Andrei Stefanescu
2024-09-13 11:05 ` Greg Kroah-Hartman
2024-09-13 12:33 ` Andrei Stefanescu
2024-09-17 17:44 ` Krzysztof Kozlowski
2024-09-18 7:57 ` Andrei Stefanescu
2024-09-18 8:13 ` Krzysztof Kozlowski [this message]
2024-09-18 9:01 ` Andrei Stefanescu
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=e9449091-bd99-46ea-9f76-bbe0ce646c5d@kernel.org \
--to=krzk@kernel.org \
--cc=andrei.stefanescu@oss.nxp.com \
--cc=brgl@bgdev.pl \
--cc=chester62515@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbrugger@suse.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=s32@nxp.com \
/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).