linux-mediatek.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Chuanhong Guo <gch981213@gmail.com>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	linux-mediatek@lists.infradead.org
Cc: "open list:STAGING SUBSYSTEM" <devel@driverdev.osuosl.org>,
	NeilBrown <neil@brown.name>,
	open list <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: 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]
Date: Sun, 9 Feb 2020 19:29:38 +0100	[thread overview]
Message-ID: <ce5bc309-8b86-9acd-5699-9b02b0fb07bf@gmail.com> (raw)
In-Reply-To: <CAJsYDVKQFB-X-mMRCZ44ypGyoWOQdSsYpfVsCPkg+TYDSw=4KQ@mail.gmail.com>



On 06/02/2020 08:53, Chuanhong Guo wrote:
> On Tue, Feb 4, 2020 at 6:37 PM Dan Carpenter <dan.carpenter@oracle.com> wrote:
>>
>> 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@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 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.
> 
> Hi Matthias and other folks on linux-mediatek:
> 
> I noticed that get_maintainers.pl reports "ARM/Mediatek SoC support"
> e-mail addreses for MTK MIPS SoCs (mt7620/mt7621/mt76x8) because of
> "mt[678]" name match in MAINTAINERS file.
> This is confusing because these MIPS SoCs clearly don't fall into
> "ARM" category. Is this an incorrect match or is it intentional? If
> it's intentional I think we should remove the confusing ARM prefix,
> and if it's incorrect we may need to figure out how to exclude
> mt7620/mt7621/mt76x8 from "ARM/Mediatek SoC support".
> 

That's a good question. I think it's an accident as I don't have good knowledge
of the MIPS architecture. Also I try to track the upstream support for MIPS as well:
https://mtk.bcnfs.org/doku.php?id=linux_mainline_effort

Regards,
Matthias

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

      reply	other threads:[~2020-02-09 18:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200204090022.123261-1-gch981213@gmail.com>
     [not found] ` <20200204094647.GS1778@kadam>
     [not found]   ` <CAJsYDV+b1bqc3b87Amo8p2UzVi4fpbRv6ytus8A5Y0r4K-X0hw@mail.gmail.com>
     [not found]     ` <20200204103456.GO11068@kadam>
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 [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=ce5bc309-8b86-9acd-5699-9b02b0fb07bf@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gch981213@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.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).