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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200204103456.GO11068@kadam>
Date:   Tue, 4 Feb 2020 13:34:57 +0300
From:   Dan Carpenter <dan.carpenter@...cle.com>
To:     Chuanhong Guo <gch981213@...il.com>
Cc:     "open list:STAGING SUBSYSTEM" <devel@...verdev.osuosl.org>,
        NeilBrown <neil@...wn.name>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] staging: mt7621-dts: add dt node for 2nd/3rd uart on
 mt7621

On Tue, Feb 04, 2020 at 05:59:21PM +0800, Chuanhong Guo wrote:
> Hi!
> 
> On Tue, Feb 4, 2020 at 5:47 PM Dan Carpenter <dan.carpenter@...cle.com> wrote:
> >
> > Please use ./scripts/get_maintainer.pl to pick the CC list and resend.
> >
> > The MAINTAINERS file says Matthias Brugger is supposed to be CC'd and
> > a couple other email lists.
> 
> According to get_maintainer.pl,  Matthias Brugger is the maintainer of
> Mediatek ARM SoC:
> 
> Matthias Brugger <matthias.bgg@...il.com> (maintainer:ARM/Mediatek SoC support)
> linux-arm-kernel@...ts.infradead.org (moderated list:ARM/Mediatek SoC support)
> linux-mediatek@...ts.infradead.org (moderated list:ARM/Mediatek SoC support)
> 
> I specifically removed the above 3 addresses because they are all for
> Mediatek ARM chips
> while mt7621 is a mips chip and belongs to ralink target under
> /arch/mips/mach-ralink.
> Code contribution for mt7621 goes through linux-mips instead of
> linux-arm or linux-mediatek,

I would have thought that we would still CC linux-mediatek?

> 
> I thinks this is an incorrect setup of get_maintainer.pl and should be
> corrected.

We could ask him...

It's always easiest to fix MAINTAINERS instead of remembering all the
exceptions and rules.

regards,
dan carpenter

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ