linux-kernel - Re: [PATCH] MAINTAINERS: add arm@...nel.org as the list for arm64 defconfig changes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 4 May 2017 10:41:54 -0500
From:   Andy Gross <andy.gross@...aro.org>
To:     Timur Tabi <timur@...eaurora.org>
Cc:     Olof Johansson <olof@...om.net>,
        Catalin Marinas <catalin.marinas@....com>,
        Will Deacon <will.deacon@....com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "arm@...nel.org" <arm@...nel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] MAINTAINERS: add arm@...nel.org as the list for arm64
 defconfig changes

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@...nel.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