From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Duje Mihanović" <duje.mihanovic@skole.hr>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Lubomir Rintel <lkundrak@v3.sk>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Kees Cook <kees@kernel.org>, Tony Luck <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
David Wronek <david@mainlining.org>,
Karel Balej <balejk@matfyz.cz>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-hardening@vger.kernel.org, phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH v14 4/4] MAINTAINERS: add myself as Marvell PXA1908 maintainer
Date: Thu, 16 Jan 2025 21:22:09 +0100 [thread overview]
Message-ID: <698cd1aa-6403-44be-9764-fbfa1db7f25e@kernel.org> (raw)
In-Reply-To: <2969840.e9J7NaK4W3@radijator>
On 16/01/2025 16:47, Duje Mihanović wrote:
>>>
>>> +ARM/Marvell PXA1908 SOC support
>>> +M: Duje Mihanović <duje.mihanovic@skole.hr>
>>> +L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
>>> +S: Maintained
>>> +T: git https://gitlab.com/LegoLivesMatter/linux
>>
>> Not sure if this was mentioned ever (it is v14, so it is likely) but if
>> that was not clear:
>>
>> Pull requests from non-kernel.org repos must be signed and your key must
>> be in kernel.org keyring. Please get your key signed
>> (meetups/conferences/keysigning map/video confcalls) and submitted to
>> the keyring.
>>
>> Patchset should be sent to soc@, as expressed in soc@ maintainer
>> profile.
>>
>> Unless this is not going to be merged by soc@, but someone from Marvell
>> maintainers, but then please drop the repo. Git repos here are for
>> managing patches.
>
> I didn't know about Git repos being used for patch management, thanks for
> letting me know.
>
> I believe this is best merged by soc@ since it is not mvebu and is the first
> arm64 MMP to be merged. However, for various reasons I'd prefer not to have my
> key signed quite yet, so would it be possible for this to get merged through
> soc@ if I removed the repo?
Merging this now is independent of signed keys, so there is no problem
in that.
But after that, if you are maintainer handling patches, then the repo
url would be useful here. It would be used for picking up patches,
because it's you who supposed to do that. SoC is not for patches from
contributors. In general SoC is only for other maintainers.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-16 20:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 20:35 [PATCH v14 0/4] Initial Marvell PXA1908 support Duje Mihanović via B4 Relay
2025-01-15 20:35 ` [PATCH v14 1/4] dt-bindings: marvell: Document PXA1908 SoC and samsung,coreprimevelte Duje Mihanović via B4 Relay
2025-01-15 20:35 ` [PATCH v14 2/4] arm64: Kconfig.platforms: Add config for Marvell PXA1908 platform Duje Mihanović via B4 Relay
2025-01-16 7:52 ` Krzysztof Kozlowski
2025-01-17 6:13 ` kernel test robot
2025-01-15 20:35 ` [PATCH v14 3/4] arm64: dts: Add DTS for Marvell PXA1908 and samsung,coreprimevelte Duje Mihanović via B4 Relay
2025-01-16 8:00 ` Krzysztof Kozlowski
2025-01-16 15:26 ` Duje Mihanović
2025-01-15 20:35 ` [PATCH v14 4/4] MAINTAINERS: add myself as Marvell PXA1908 maintainer Duje Mihanović via B4 Relay
2025-01-16 7:56 ` Krzysztof Kozlowski
2025-01-16 15:47 ` Duje Mihanović
2025-01-16 20:22 ` Krzysztof Kozlowski [this message]
2025-01-16 14:02 ` [PATCH v14 0/4] Initial Marvell PXA1908 support Rob Herring (Arm)
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=698cd1aa-6403-44be-9764-fbfa1db7f25e@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@lunn.ch \
--cc=balejk@matfyz.cz \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=david@mainlining.org \
--cc=devicetree@vger.kernel.org \
--cc=duje.mihanovic@skole.hr \
--cc=gpiccoli@igalia.com \
--cc=gregory.clement@bootlin.com \
--cc=kees@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tony.luck@intel.com \
--cc=will@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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