From: Olof Johansson <olof@lixom.net>
To: Marc Gonzalez <marc.w.gonzalez@free.fr>
Cc: Mark Rutland <mark.rutland@arm.com>,
Heiko Stuebner <heiko@sntech.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
arm-soc <arm@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] MAINTAINERS: List arch/arm64/configs/ explicitly
Date: Sun, 28 Apr 2019 23:32:42 -0700 [thread overview]
Message-ID: <20190429063242.blpen7vuuripsf56@localhost> (raw)
In-Reply-To: <4097b949-f285-b490-23cc-a8b4d9d37edf@free.fr>
On Thu, Apr 18, 2019 at 07:48:15PM +0200, Marc Gonzalez wrote:
> On 18/04/2019 19:25, Olof Johansson wrote:
>
> > On Thu, Apr 18, 2019 at 6:53 AM Marc Gonzalez wrote:
> >>
> >> As it stands, get_maintainer.pl scans the changelog to determine the
> >> recipients for arm64 defconfig patches:
> >>
> >> $ scripts/get_maintainer.pl arch/arm64/configs/defconfig
> >> Catalin Marinas <catalin.marinas@arm.com> (maintainer:ARM64 PORT (AARCH64 ARCHITECTURE))
> >> Will Deacon <will.deacon@arm.com> (maintainer:ARM64 PORT (AARCH64 ARCHITECTURE))
> >> Heiko Stuebner <heiko@sntech.de> (commit_signer:10/73=14%)
> >> Simon Horman <horms+renesas@verge.net.au> (commit_signer:9/73=12%)
> >> Maxime Ripard <maxime.ripard@bootlin.com> (commit_signer:8/73=11%)
> >> Olof Johansson <olof@lixom.net> (commit_signer:8/73=11%,added_lines:39/248=16%,removed_lines:63/135=47%)
> >> Andy Gross <andy.gross@linaro.org> (commit_signer:8/73=11%)
> >> Jagan Teki <jagan@amarulasolutions.com> (authored:7/73=10%)
> >> Bjorn Andersson <bjorn.andersson@linaro.org> (authored:7/73=10%,added_lines:32/248=13%)
> >> Enric Balletbo i Serra <enric.balletbo@collabora.com> (authored:5/73=7%,added_lines:29/248=12%)
> >> Stefan Wahren <stefan.wahren@i2se.com> (authored:4/73=5%)
> >> Ezequiel Garcia <ezequiel@collabora.com> (authored:4/73=5%)
> >> Marc Gonzalez <marc.w.gonzalez@free.fr> (added_lines:53/248=21%,removed_lines:63/135=47%)
> >> linux-arm-kernel@lists.infradead.org (moderated list:ARM64 PORT (AARCH64 ARCHITECTURE))
> >> linux-kernel@vger.kernel.org (open list)
> >>
> >> Explicitly list arch/arm64/configs/ in order to limit the recipients
> >> list to AArch64 maintainers, and protect the innocent:
> >>
> >> $ scripts/get_maintainer.pl arch/arm64/configs/defconfig
> >> Catalin Marinas <catalin.marinas@arm.com> (maintainer:ARM64 PORT (AARCH64 ARCHITECTURE))
> >> Will Deacon <will.deacon@arm.com> (maintainer:ARM64 PORT (AARCH64 ARCHITECTURE))
> >> linux-arm-kernel@lists.infradead.org (moderated list:ARM64 PORT (AARCH64 ARCHITECTURE))
> >> linux-kernel@vger.kernel.org (open list)
> >>
> >> Signed-off-by: Marc Gonzalez <marc.w.gonzalez@free.fr>
> >
> > This is inaccurate, most defconfig updates come in through arm-soc
> > since most of them are platform related.
>
> What is inaccurate? My assessment of the situation?
> ("As it stands, get_maintainer.pl scans the changelog to determine
> the recipients for arm64 defconfig patches.")
The list of maintainers is inaccurate.
In general, defconfig updates should go in through the respective platform
maintainers for platform-related changes. For architecture related changes,
it'll go through Catalin/Will).
> > For core features, Will and Catalin are there right maintainers. For
> > platform options, they usually go to the platform maintainers and then
> > to us.
> >
> > So, if you're turning on a feature for an SoC, send it to said
> > SoC/platform maintainer.
>
> I want to stop receiving defconfig patches, just because I poked
> the file a few months ago.
The way maintenance of the file is setup, there's no good way to write
a maintainer entry for it. None of us want these patches directly.
We've dealt with this just fine for years on 32-bit ARM.
Feel free to just delete these patches when you receive them.
-Olof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-04-29 7:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 12:50 [PATCH v1] MAINTAINERS: Add ARM64 DEFCONFIG entry Marc Gonzalez
2019-04-18 13:01 ` Mark Rutland
2019-04-18 13:10 ` Catalin Marinas
2019-04-18 13:53 ` [PATCH v2] MAINTAINERS: List arch/arm64/configs/ explicitly Marc Gonzalez
2019-04-18 17:25 ` Olof Johansson
2019-04-18 17:48 ` Marc Gonzalez
2019-04-29 6:32 ` Olof Johansson [this message]
2019-04-29 8:00 ` Marc Gonzalez
2019-04-23 9:56 ` Marc Gonzalez
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=20190429063242.blpen7vuuripsf56@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.w.gonzalez@free.fr \
--cc=mark.rutland@arm.com \
--cc=will.deacon@arm.com \
/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