From: Krzysztof Kozlowski <krzk@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
soc@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Catalin Marinas <catalin.marinas@arm.com>,
arm@kernel.org
Subject: Re: [RFC 2/2] MAINTAINERS: add a limited ARM and ARM64 SoC entry
Date: Tue, 1 Dec 2020 23:20:41 +0200 [thread overview]
Message-ID: <20201201212041.GB23379@kozik-lap> (raw)
In-Reply-To: <20201201211516.24921-2-krzk@kernel.org>
On Tue, Dec 01, 2020 at 11:15:16PM +0200, Krzysztof Kozlowski wrote:
> It is expected for ARM and ARM64 SoC related code to go through
> sub-architecture maintainers. Their addresses were therefore not
I reshaped my message last moment and missed that it does not make
sense anymore... It should be:
"The ARM and ARM64 SoC maintainers addresses were therefore not..."
Best regards,
Krzysztof
> documented to push patch traffic through sub-architecture maintainers.
>
> However when patches touch generic code, e.g. multi_v7_defconfig, the
> patch might not be picked up by them and instead should go to the SoC
> maintainers - Arnd and Olof.
>
> Add a minimal maintainer's entry for SoC covering only Makefile, so it
> will not appear on most of submissions (except new devicetree boards).
> It will though serve as a documentation and reference for cases when
> submitter does not know where to send his SoC-related patches.
>
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> ---
> MAINTAINERS | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 6149066a545e..f302983645bd 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1491,6 +1491,16 @@ F: Documentation/devicetree/bindings/iommu/arm,smmu*
> F: drivers/iommu/arm/
> F: drivers/iommu/io-pgtable-arm*
>
> +ARM AND ARM64 SoC SUB-ARCHITECTURES (COMMON PARTS)
> +M: Arnd Bergmann <arnd@arndb.de>
> +M: Olof Johansson <olof@lixom.net>
> +M: soc@kernel.org
> +L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> +S: Maintained
> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git
> +F: arch/arm/boot/dts/Makefile
> +F: arch/arm64/boot/dts/Makefile
> +
> ARM SUB-ARCHITECTURES
> L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> S: Maintained
> --
> 2.25.1
>
parent reply other threads:[~2020-12-01 21:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20201201211516.24921-2-krzk@kernel.org>]
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=20201201212041.GB23379@kozik-lap \
--to=krzk@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--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).