All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Conor Dooley <conor.dooley@microchip.com>
Cc: soc@kernel.org
Subject: Re: [PATCH v3] Documentation/process: add soc maintainer handbook
Date: Tue, 06 Jun 2023 20:40:24 +0000	[thread overview]
Message-ID: <168608402448.20407.264145201677581136.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230606-escapable-stuffed-7ca5033e7741@wendy>

Hello:

This patch was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:

On Tue, 6 Jun 2023 09:27:43 +0100 you 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.
> 
> [...]

Here is the summary with links:
  - [v3] Documentation/process: add soc maintainer handbook
    https://git.kernel.org/soc/soc/c/425d827ef91e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-06-06 20:40 UTC|newest]

Thread overview: 13+ 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  8:27 ` Conor Dooley
2023-06-06  8:27 ` Conor Dooley
2023-06-06 10:23 ` Arnd Bergmann
2023-06-06 10:23   ` Arnd Bergmann
2023-06-06 10:23   ` Arnd Bergmann
2023-06-17 18:32   ` Conor Dooley
2023-06-17 18:32     ` Conor Dooley
2023-06-17 18:32     ` Conor Dooley
2023-06-17 20:29     ` Krzysztof Kozlowski
2023-06-17 20:29       ` Krzysztof Kozlowski
2023-06-17 20:29       ` Krzysztof Kozlowski
2023-06-06 20:40 ` patchwork-bot+linux-soc [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=168608402448.20407.264145201677581136.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=conor.dooley@microchip.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.