From: Chuanhong Guo <gch981213@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: "open list:STAGING SUBSYSTEM" <devel@driverdev.osuosl.org>,
NeilBrown <neil@brown.name>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: mt7621-dts: add dt node for 2nd/3rd uart on mt7621
Date: Tue, 4 Feb 2020 17:59:21 +0800 [thread overview]
Message-ID: <CAJsYDV+b1bqc3b87Amo8p2UzVi4fpbRv6ytus8A5Y0r4K-X0hw@mail.gmail.com> (raw)
In-Reply-To: <20200204094647.GS1778@kadam>
Hi!
On Tue, Feb 4, 2020 at 5:47 PM Dan Carpenter <dan.carpenter@oracle.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@gmail.com> (maintainer:ARM/Mediatek SoC support)
linux-arm-kernel@lists.infradead.org (moderated list:ARM/Mediatek SoC support)
linux-mediatek@lists.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 thinks this is an incorrect setup of get_maintainer.pl and should be
corrected.
Regards,
Chuanhong Guo
next prev parent reply other threads:[~2020-02-04 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 8:59 [PATCH] staging: mt7621-dts: add dt node for 2nd/3rd uart on mt7621 Chuanhong Guo
2020-02-04 9:46 ` Dan Carpenter
2020-02-04 9:59 ` Chuanhong Guo [this message]
2020-02-04 10:34 ` Dan Carpenter
2020-02-06 7:53 ` Are people from linux-mediatek also interested in Mediatek MIPS SoCs? [Was: [PATCH] staging: mt7621-dts: add dt node for 2nd/3rd uart on mt7621] Chuanhong Guo
2020-02-09 18:29 ` Matthias Brugger
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=CAJsYDV+b1bqc3b87Amo8p2UzVi4fpbRv6ytus8A5Y0r4K-X0hw@mail.gmail.com \
--to=gch981213@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@brown.name \
/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).