Linux SOC development
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: soc@kernel.org
Subject: Re: [PATCH] MAINTAINERS: exclude defconfig from ARM64 PORT
Date: Mon, 01 Sep 2025 10:30:05 +0000	[thread overview]
Message-ID: <175672260500.3678624.4210459096985387469.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250818-arm64-defconfig-v1-1-f589553c3d72@collabora.com>

Hello:

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

On Mon, 18 Aug 2025 23:08:04 +0200 you wrote:
> Patches for the arm64 defconfig are supposed to be sent to the
> SoC maintainers (e.g. a change in the generic arm64 defconfig
> required for Rockchip devices should be send to Heiko Stübner
> as he is listed as maintainer for "ARM/Rockchip SoC support")
> and not the ARM64 PORT maintainers.
> 
> While we cannot easily describe this in MAINTAINERS, we can at
> least stop it from giving false information and make it behave
> the same way as for the MAINTAINERS file itself (which basically
> has the same rules), so that it just outputs the LKML for the
> ARM64 defconfig.
> 
> [...]

Here is the summary with links:
  - MAINTAINERS: exclude defconfig from ARM64 PORT
    https://git.kernel.org/soc/soc/c/750b54513f69

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



      parent reply	other threads:[~2025-09-01 10:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 21:08 [PATCH] MAINTAINERS: exclude defconfig from ARM64 PORT Sebastian Reichel
2025-08-19  8:39 ` Will Deacon
2025-08-19  8:44 ` Catalin Marinas
2025-09-01 10:30 ` 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=175672260500.3678624.4210459096985387469.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=sebastian.reichel@collabora.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