From: Jonathan Corbet <corbet@lwn.net>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
soc@kernel.org, linux-arm-kernel@lists.infradead.org,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.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>,
"Conor Dooley" <conor@kernel.org>,
"Heiko Stübner" <heiko@sntech.de>
Subject: Re: [PATCH v2] Documentation/process: maintainer-soc: clarify submitting patches
Date: Mon, 07 Oct 2024 11:18:29 -0600 [thread overview]
Message-ID: <87wmijj0gq.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20240925095635.30452-1-krzysztof.kozlowski@linaro.org>
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> writes:
> 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.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Kevin Hilman <khilman@baylibre.com>
> Cc: Palmer Dabbelt <palmer@dabbelt.com>
> Cc: Geert Uytterhoeven <geert+renesas@glider.be>
> Cc: Conor Dooley <conor@kernel.org>
> Cc: Heiko Stübner <heiko@sntech.de>
>
> ---
>
> During our LPC ad-hoc BoF, we discussed improving Maintainer SoC docs
> and I think I volunteered to write something. The trouble is that
> whatever I won't write in my notes, escapes my memory.
>
> I believe this is what we discussed. Was there anything more to
> write/document?
>
> Changes in v2:
> 1. Fix missing closing ) (Conor).
> 2. Style changes (in point 3.).
> 3. Soften note that soc@kernel is not for discussing ("is usually not").
> ---
> Documentation/process/maintainer-soc.rst | 42 +++++++++++++++++++++---
> 1 file changed, 37 insertions(+), 5 deletions(-)
Applied, thanks.
jon
next prev parent reply other threads:[~2024-10-07 17:18 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
2024-10-07 17:18 ` Jonathan Corbet [this message]
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=87wmijj0gq.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=conor@kernel.org \
--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