linux-kernel - Re: [PATCH v14 4/4] MAINTAINERS: add myself as Marvell PXA1908 maintainer

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: <698cd1aa-6403-44be-9764-fbfa1db7f25e@kernel.org>
Date: Thu, 16 Jan 2025 21:22:09 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Duje Mihanović <duje.mihanovic@...le.hr>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Lubomir Rintel <lkundrak@...sk>,
 Catalin Marinas <catalin.marinas@....com>, Will Deacon <will@...nel.org>,
 Andrew Lunn <andrew@...n.ch>, Gregory Clement <gregory.clement@...tlin.com>,
 Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
 Kees Cook <kees@...nel.org>, Tony Luck <tony.luck@...el.com>,
 "Guilherme G. Piccoli" <gpiccoli@...lia.com>,
 David Wronek <david@...nlining.org>, Karel Balej <balejk@...fyz.cz>,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, linux-hardening@...r.kernel.org,
 phone-devel@...r.kernel.org, ~postmarketos/upstreaming@...ts.sr.ht
Subject: Re: [PATCH v14 4/4] MAINTAINERS: add myself as Marvell PXA1908
 maintainer

On 16/01/2025 16:47, Duje Mihanović wrote:
>>>
>>> +ARM/Marvell PXA1908 SOC support
>>> +M:	Duje Mihanović <duje.mihanovic@...le.hr>
>>> +L:	linux-arm-kernel@...ts.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