linux-kernel - Re: [PATCH] Documentation/process: maintainer-soc: clarify submitting patches

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] [day] [month] [year] [list]

Message-ID: <20240924-powdery-driver-e66ea543d634@spud>
Date: Tue, 24 Sep 2024 14:19:12 +0100
From: Conor Dooley <conor@...nel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
	soc@...nel.org, Jonathan Corbet <corbet@....net>,
	linux-arm-kernel@...ts.infradead.org, workflows@...r.kernel.org,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	Linus Walleij <linus.walleij@...aro.org>,
	Alexandre Belloni <alexandre.belloni@...tlin.com>,
	Will Deacon <will@...nel.org>, Kevin Hilman <khilman@...libre.com>,
	Palmer Dabbelt <palmer@...belt.com>,
	Geert Uytterhoeven <geert+renesas@...der.be>,
	Heiko Stübner <heiko@...ech.de>
Subject: Re: [PATCH] Documentation/process: maintainer-soc: clarify
 submitting patches

On Tue, Sep 24, 2024 at 03:08:31PM +0200, Krzysztof Kozlowski wrote:

>  Most of these submaintainers have their own trees where they stage patches,
>  sending pull requests to the main SoC tree.  These trees are usually, but not
> -always, listed in MAINTAINERS.  The main SoC maintainers can be reached via the
> -alias soc@...nel.org if there is no platform-specific maintainer, or if they
> -are unresponsive.
> +always, listed in MAINTAINERS.

I probably had some specific case in mind with that original wording. I
presume it still holds true for some smaller platforms, but I cannot
remember the specific case that prompted it. I'll have to see if I can
figure out which platforms they are (if any) and get the tree added.

Cheers,
Conor.

>  What the SoC tree is not, however, is a location for architecture-specific code
>  changes.  Each architecture has its own maintainers that are responsible for
>  architectural details, CPU errata and the like.
>  
> +Submitting Patches for Given SoC
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +All usual platform related patches should be sent via SoC submaintainers
> +(platform-specific maintainers.  This includes also changes to per-platform or
   ^ this is unclosed.

> +shared defconfigs (scripts/get_maintainer.pl might not provide correct
> +addresses in such case).

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)