From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Conor Dooley <conor@kernel.org>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Olof Johansson" <olof@lixom.net>,
soc@kernel.org, "Jonathan Corbet" <corbet@lwn.net>,
linux-arm-kernel@lists.infradead.org, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
"Linus Walleij" <linus.walleij@linaro.org>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Will Deacon" <will@kernel.org>,
"Kevin Hilman" <khilman@baylibre.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Heiko Stübner" <heiko@sntech.de>
Subject: Re: [PATCH] Documentation/process: maintainer-soc: clarify submitting patches
Date: Wed, 25 Sep 2024 11:54:43 +0200 [thread overview]
Message-ID: <f1f5f503-b927-4bfe-b55d-d8fd343a2ba1@linaro.org> (raw)
In-Reply-To: <20240924-powdery-driver-e66ea543d634@spud>
On 24/09/2024 15:19, Conor Dooley wrote:
> 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.
Ack. I have v2 with minor text changes in other places as well. I will
send soon.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-09-25 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 13:08 Krzysztof Kozlowski
2024-09-24 13:19 ` Conor Dooley
2024-09-25 9:54 ` Krzysztof Kozlowski [this message]
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=f1f5f503-b927-4bfe-b55d-d8fd343a2ba1@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=geert+renesas@glider.be \
--cc=heiko@sntech.de \
--cc=khilman@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=palmer@dabbelt.com \
--cc=soc@kernel.org \
--cc=will@kernel.org \
--cc=workflows@vger.kernel.org \
/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