From: "Arnd Bergmann" <arnd@arndb.de>
To: "Conor.Dooley" <conor.dooley@microchip.com>, soc@kernel.org
Cc: "Conor Dooley" <conor@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
devicetree@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
"Olof Johansson" <olof@lixom.net>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v3] Documentation/process: add soc maintainer handbook
Date: Tue, 06 Jun 2023 12:23:26 +0200 [thread overview]
Message-ID: <05c50d10-080b-43ab-9131-98f71508ac2d@app.fastmail.com> (raw)
In-Reply-To: <20230606-escapable-stuffed-7ca5033e7741@wendy>
On Tue, Jun 6, 2023, at 10:27, Conor Dooley wrote:
> Arnd suggested that adding a maintainer handbook for the SoC "subsystem"
> would be helpful in trying to bring on board maintainers for the various
> new platforms cropping up in RISC-V land.
>
> Add a document briefly describing the role of the SoC subsystem and some
> basic advice for (new) platform maintainers.
>
> Suggested-by: Arnd Bergmann <arnd@arndb.de>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> Changes in v3:
> - sort out a rake of spelling/grammar bits spotted by Randy, apart from
> the one noted as a suggestion
> - drop the refs for document filepaths
Thanks, I've applied this in the soc/newsoc branch of the soc tree
now, which is where I'm already queuing new platforms.
Arnd
next prev parent reply other threads:[~2023-06-06 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 8:27 [PATCH v3] Documentation/process: add soc maintainer handbook Conor Dooley
2023-06-06 10:23 ` Arnd Bergmann [this message]
[not found] ` <20230617-succulent-surgery-3dbbf9454737@spud>
2023-06-17 20:29 ` 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=05c50d10-080b-43ab-9131-98f71508ac2d@app.fastmail.com \
--to=arnd@arndb.de \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=olof@lixom.net \
--cc=palmer@dabbelt.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=soc@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;
as well as URLs for NNTP newsgroup(s).