Linux SOC development
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Kevin Hilman <khilman@baylibre.com>
Cc: soc@kernel.org
Subject: Re: [PATCH] MAINTAINERS: ARM/Amlogic SoCs: add Neil as primary maintainer
Date: Mon, 17 May 2021 20:20:09 +0000	[thread overview]
Message-ID: <162128280972.19328.14012577360413699130.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210511190054.26300-1-khilman@baylibre.com>

Hello:

This patch was applied to soc/soc.git (refs/heads/arm/fixes):

On Tue, 11 May 2021 12:00:54 -0700 you wrote:
> Add Neil as primary maintainer for the Amlogic family of Arm SoCs.  I
> will now act as co-maintainer.
> 
> Neil is already doing lots of the reviewing, testing and behind the
> scenes support for users of the upstream kernel on these SoCs, so this
> is just to formalize the current state of affairs.
> 
> [...]

Here is the summary with links:
  - MAINTAINERS: ARM/Amlogic SoCs: add Neil as primary maintainer
    https://git.kernel.org/soc/soc/c/b433d090ac63

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



      parent reply	other threads:[~2021-05-17 20:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-11 19:00 [PATCH] MAINTAINERS: ARM/Amlogic SoCs: add Neil as primary maintainer Kevin Hilman
2021-05-11 19:00 ` Kevin Hilman
2021-05-11 19:00 ` Kevin Hilman
2021-05-14  7:37 ` Neil Armstrong
2021-05-14  7:37   ` Neil Armstrong
2021-05-14  7:37   ` Neil Armstrong
2021-05-16 16:56 ` Martin Blumenstingl
2021-05-16 16:56   ` Martin Blumenstingl
2021-05-16 16:56   ` Martin Blumenstingl
2021-05-16 16:56   ` Martin Blumenstingl
2021-05-17 20:20 ` 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=162128280972.19328.14012577360413699130.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=khilman@baylibre.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox