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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux