Thread (3 messages) 3 messages, 2 authors, 2024-09-25

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

From: Conor Dooley <conor@kernel.org>
Date: 2024-09-24 13:19:18
Also in: linux-doc, lkml, workflows

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@kernel.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).

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help