From: Will Deacon <will@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
soc@lists.linux.dev, Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH] MAINTAINERS: exclude defconfig from ARM64 PORT
Date: Tue, 19 Aug 2025 09:39:29 +0100 [thread overview]
Message-ID: <aKQ4QSAqT7OLIBf1@willie-the-truck> (raw)
In-Reply-To: <20250818-arm64-defconfig-v1-1-f589553c3d72@collabora.com>
On Mon, Aug 18, 2025 at 11:08:04PM +0200, Sebastian Reichel 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.
>
> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index daf520a13bdf6a991c0160a96620f40308c29ee0..b6466a628381bf40ebcf7e3638ec65fabf6ad357 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -3667,6 +3667,7 @@ F: drivers/virt/coco/arm-cca-guest/
> F: drivers/virt/coco/pkvm-guest/
> F: tools/testing/selftests/arm64/
> X: arch/arm64/boot/dts/
> +X: arch/arm64/configs/defconfig
Acked-by: Will Deacon <will@kernel.org>
Will
next prev parent reply other threads:[~2025-08-19 10:12 UTC|newest]
Thread overview: 3+ 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 [this message]
2025-08-19 8:44 ` Catalin Marinas
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=aKQ4QSAqT7OLIBf1@willie-the-truck \
--to=will@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=soc@lists.linux.dev \
/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