netdev - Re: [PATCH net] MAINTAINERS: Gary Zambrano's email is bouncing

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]

Date:   Sat, 17 Sep 2016 16:39:29 -0700
From:   Michael Chan <michael.chan@...adcom.com>
To:     Florian Fainelli <f.fainelli@...il.com>
Cc:     Joe Perches <joe@...ches.com>, netdev <netdev@...r.kernel.org>,
        David Miller <davem@...emloft.net>,
        bcm-kernel-feedback-list <bcm-kernel-feedback-list@...adcom.com>,
        Rafał Miłecki <zajec5@...il.com>,
        Hauke Mehrtens <hauke@...ke-m.de>
Subject: Re: [PATCH net] MAINTAINERS: Gary Zambrano's email is bouncing

On Sat, Sep 17, 2016 at 4:17 PM, Florian Fainelli <f.fainelli@...il.com> wrote:
> 2016-09-17 15:51 GMT-07:00 Joe Perches <joe@...ches.com>:
>> On Sat, 2016-09-17 at 15:27 -0700, Florian Fainelli wrote:
>>> Gary has not been with Broadcom for some time now, replace his address
>>> with the internal mailing-list used for other entries.
>>>
>>> > Signed-off-by: Florian Fainelli <f.fainelli@...il.com>
>>> ---
>>> Michael,
>>>
>>> Since this is an old driver, not sure who could step up as a maintainer
>>> for b44?
>> []
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>> []
>>> @@ -2500,8 +2500,8 @@ S:      Supported
>>
>>> F:    kernel/bpf/
>>>
>>>  BROADCOM B44 10/100 ETHERNET DRIVER
>>> -M:   Gary Zambrano <zambrano@...adcom.com>
>>>  L:   netdev@...r.kernel.org
>>> +M:   bcm-kernel-feedback-list@...adcom.com
>>>  S:   Supported
>>>  F:   drivers/net/ethernet/broadcom/b44.*
>>
>> Without an actual maintainer, this should really be
>> orphan and not supported.
>
> I would like to hear from Michael before concluding that
>

I have worked on this NIC more than 10 years ago.  Last time I
checked, I don't have this NIC anymore after moving offices several
times.

I don't mind being the maintainer, if no one else more suitable and
have access to hardware wants to do it.