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: <CAC3K-4obNm0LLzsirCqZF9xY-Bwv---m5MeSQuv5Q65=gsngnQ@mail.gmail.com>
Date:   Wed, 8 Feb 2017 18:34:00 -0500
From:   Jon Mason <jon.mason@...adcom.com>
To:     Rafał Miłecki <rafal@...ecki.pl>
Cc:     Florian Fainelli <f.fainelli@...il.com>,
        Hauke Mehrtens <hauke@...ke-m.de>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        open list <linux-kernel@...r.kernel.org>,
        BCM Kernel Feedback <bcm-kernel-feedback-list@...adcom.com>
Subject: Re: [PATCH] MAINTAINERS: Add Jon Mason to BCM5301X maintainers

On Wed, Feb 8, 2017 at 6:29 PM, Rafał Miłecki <rafal@...ecki.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@...adcom.com>
>
>
> Acked-by: Rafał Miłecki <rafal@...ecki.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@...ke-m.de>
>>  M:     Rafał Miłecki <zajec5@...il.com>
>> +M:     Jon Mason <jonmason@...adcom.com>
>>  M:     bcm-kernel-feedback-list@...adcom.com
>>  L:     linux-arm-kernel@...ts.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

Thanks,
Jon

>
>
> Is it worth using N: (regex pattern)? Just asking.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ