From: andy.gross@linaro.org (Andy Gross)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: add arm@kernel.org as the list for arm64 defconfig changes
Date: Thu, 4 May 2017 10:41:54 -0500 [thread overview]
Message-ID: <20170504154154.GA13706@hector.attlocal.net> (raw)
In-Reply-To: <0ad7d305-d323-339f-9534-d559f1cf656a@codeaurora.org>
On Wed, May 03, 2017 at 12:47:16PM -0500, Timur Tabi wrote:
> On 05/03/2017 12:39 PM, Olof Johansson wrote:
> > No, I'm not saying that, and there is a better way: Send it through
> > Andy if in doubt -- it should be his job as your platform maintainer
> > to help guide you through the system if needed.
>
> Will told me that defconfig patches should go to arm at kernel.org, but you're
> telling me they should go to Andy instead.
>
> Andy's being the platform maintainer is news to me. I'm not saying he
> isn't, but I can't remember the last time I involved him in any patches of ours.
If it is Qualcomm related, it generally goes through me. And I send it up
through the arm soc guys (kevin, olof, and arnd).
>
> Either way, I think there should be a designated maintainer for
> arch/arm64/configs/defconfig, and I think that person/alias should be in
> MAINTAINERS.
I disagree here. We've generally had defconfigs go up through the disparate ARM
board maintainers and they get collated by arm-soc. It's easy when it's
something like qcom_defconfig, but get_maintainer doesn't give you the correct
name if you are going for multiv7 or some of the default configs.
Andy
prev parent reply other threads:[~2017-05-04 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 16:31 [PATCH] MAINTAINERS: add arm@kernel.org as the list for arm64 defconfig changes Timur Tabi
2017-05-03 16:34 ` Russell King - ARM Linux
2017-05-03 17:01 ` Catalin Marinas
2017-05-03 17:08 ` Timur Tabi
2017-05-03 17:14 ` Catalin Marinas
2017-05-03 17:26 ` Olof Johansson
2017-05-03 17:33 ` Timur Tabi
2017-05-03 17:39 ` Olof Johansson
2017-05-03 17:47 ` Timur Tabi
2017-05-04 10:21 ` Will Deacon
2017-05-04 15:41 ` Andy Gross [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=20170504154154.GA13706@hector.attlocal.net \
--to=andy.gross@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).