From: Timur Tabi <timur@codeaurora.org>
To: Olof Johansson <olof@lixom.net>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
"arm@kernel.org" <arm@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Will Deacon <will.deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andy Gross <andy.gross@linaro.org>
Subject: Re: [PATCH] MAINTAINERS: add arm@kernel.org as the list for arm64 defconfig changes
Date: Wed, 3 May 2017 12:47:16 -0500 [thread overview]
Message-ID: <0ad7d305-d323-339f-9534-d559f1cf656a@codeaurora.org> (raw)
In-Reply-To: <CAOesGMgnOQXtLT8aUvPhXDfShzhkP-3LWFhP60xiMn65x6aq=w@mail.gmail.com>
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@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.
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.
> Sometimes we tweak defconfigs late in the merge window and sometimes
> even during early -rc, so let us get back to this after we've handled
> the merges.
Ok, thank you.
--
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
Technologies, Inc. Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-05-03 17:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 16:31 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 [this message]
2017-05-04 10:21 ` Will Deacon
2017-05-04 15:41 ` Andy Gross
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=0ad7d305-d323-339f-9534-d559f1cf656a@codeaurora.org \
--to=timur@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=arm@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--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
Powered by JetHome