From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: Add Jon Mason to BCM5301X maintainers
Date: Wed, 8 Feb 2017 15:37:41 -0800 [thread overview]
Message-ID: <ffaf7ac4-cf2f-efb8-27b3-b8efbe290b34@gmail.com> (raw)
In-Reply-To: <CAC3K-4rXAi_1aYg37of60acAh8PsuCaDUtrh0CvkkVdwKP0Fgg@mail.gmail.com>
On 02/08/2017 03:37 PM, Jon Mason wrote:
> On Wed, Feb 8, 2017 at 6:35 PM, Rafa? Mi?ecki <rafal@milecki.pl> wrote:
>> On 2017-02-09 00:34, Jon Mason wrote:
>>>
>>> On Wed, Feb 8, 2017 at 6:29 PM, Rafa? Mi?ecki <rafal@milecki.pl> wrote:
>>>>
>>>> On 02/09/2017 12:22 AM, Jon Mason wrote:
>>>>>
>>>>>
>>>>> Adding myself as a maintainer for Broadcom Northstar SoCs. Also, adding
>>>>> a regex entry to discover the SVK DTs already present.
>>>>>
>>>>> Signed-off-by: Jon Mason <jon.mason@broadcom.com>
>>>>
>>>>
>>>>
>>>> Acked-by: Rafa? Mi?ecki <rafal@milecki.pl>
>>>>
>>>>
>>>>> MAINTAINERS | 2 ++
>>>>> 1 file changed, 2 insertions(+)
>>>>>
>>>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>>>> index 2abda6c..03c1760 100644
>>>>> --- a/MAINTAINERS
>>>>> +++ b/MAINTAINERS
>>>>> @@ -2641,12 +2641,14 @@ F: arch/mips/include/asm/mach-bcm47xx/*
>>>>> BROADCOM BCM5301X ARM ARCHITECTURE
>>>>> M: Hauke Mehrtens <hauke@hauke-m.de>
>>>>> M: Rafa? Mi?ecki <zajec5@gmail.com>
>>>>> +M: Jon Mason <jonmason@broadcom.com>
>>>>> M: bcm-kernel-feedback-list at broadcom.com
>>>>> L: linux-arm-kernel at lists.infradead.org
>>>>> S: Maintained
>>>>> F: arch/arm/mach-bcm/bcm_5301x.c
>>>>> F: arch/arm/boot/dts/bcm5301x*.dtsi
>>>>> F: arch/arm/boot/dts/bcm470*
>>>>> +N: bcm953012
>>>
>>>
>>> There are 2 now, and a 3rd one coming soon.
>>> ./arch/arm/boot/dts/bcm953012k.dts
>>> ./arch/arm/boot/dts/bcm953012er.dts
>>>
>>> It might be overkill, but I thought it was the way everyone was going
>>> (and seems to be more elegant). I'll defer if the simpler version is
>>> desired
>>
>>
>> Maybe
>> F: arch/arm/boot/dts/bcm953012*
>> would be sufficient and more efficient?
>
> Works for me.
>
> Florian, you want a v2 or did you want to massage the patch by hand?
I am very lazy, so I need a v2, thanks!
--
Florian
next prev parent reply other threads:[~2017-02-08 23:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 23:22 [PATCH] MAINTAINERS: Add Jon Mason to BCM5301X maintainers Jon Mason
2017-02-08 23:29 ` Rafał Miłecki
2017-02-08 23:34 ` Jon Mason
2017-02-08 23:35 ` Rafał Miłecki
2017-02-08 23:37 ` Jon Mason
2017-02-08 23:37 ` Florian Fainelli [this message]
2017-02-08 23:40 ` Rafał Miłecki
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=ffaf7ac4-cf2f-efb8-27b3-b8efbe290b34@gmail.com \
--to=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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