From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
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
Cc: "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>,
"Conor Dooley" <conor@kernel.org>,
"Heiko Stübner" <heiko@sntech.de>
Subject: Re: [PATCH v2] Documentation/process: maintainer-soc: clarify submitting patches
Date: Sat, 5 Oct 2024 06:44:36 +0700 [thread overview]
Message-ID: <ZwB95FxdgqAtuc7z@archie.me> (raw)
In-Reply-To: <20240925095635.30452-1-krzysztof.kozlowski@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 432 bytes --]
On Wed, Sep 25, 2024 at 11:56:35AM +0200, Krzysztof Kozlowski wrote:
> Patches for SoCs are expected to be picked up by SoC submaintainers.
> The main SoC maintainers should be addressed only in few cases.
>
> Rewrite the section about maintainer handling to document above
> expectation.
>
LGTM, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-10-04 23:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 9:56 Krzysztof Kozlowski
2024-10-02 13:02 ` Linus Walleij
2024-10-04 22:09 ` Kevin Hilman
2024-10-04 23:44 ` Bagas Sanjaya [this message]
2024-10-07 17:18 ` Jonathan Corbet
2024-10-11 12:40 ` Krzysztof Kozlowski
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=ZwB95FxdgqAtuc7z@archie.me \
--to=bagasdotme@gmail.com \
--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=krzysztof.kozlowski@linaro.org \
--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