From: Florian Fainelli <f.fainelli@gmail.com>
To: David Miller <davem@davemloft.net>, joe@perches.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] MAINTAINERS: PHY: Change maintainer to reviewer
Date: Wed, 25 Nov 2015 10:07:25 -0800 [thread overview]
Message-ID: <5655F8DD.3000405@gmail.com> (raw)
In-Reply-To: <20151125.113602.515197415619267019.davem@davemloft.net>
On 25/11/15 08:36, David Miller wrote:
> From: Joe Perches <joe@perches.com>
> Date: Tue, 24 Nov 2015 17:04:11 -0800
>
>> On Tue, 2015-11-24 at 15:29 -0800, Florian Fainelli wrote:
>>> Now that there is a reviewer role, add myself as reviewer since the PHY
>>> library code is maintained via the networking tree.
>>
>> []
>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>> []
>>> @@ -4195,7 +4195,7 @@ F: include/linux/netfilter_bridge/
>>> F:> > net/bridge/
>>>
>>> ETHERNET PHY LIBRARY
>>> -M: Florian Fainelli <f.fainelli@gmail.com>
>>> +R: Florian Fainelli <f.fainelli@gmail.com>
>>> L: netdev@vger.kernel.org
>>> S: Maintained
>>> F: include/linux/phy.h
>>
>> Just because the upstream path is not a tree you
>> manage doesn't mean you aren't a maintainer.
>>
>> I think the status should be something other than
>> "Maintained" if you are not the maintainer.
>
> Yeah, I kinda agree, Florian you are pretty much the de-facto
> maintainer and I usually wait for you to review any PHY library
> changes before applying them unless they are _really_ obvious.
Sounds good, let's drop this patch then, thanks!
--
Florian
prev parent reply other threads:[~2015-11-25 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 23:29 [PATCH net-next] MAINTAINERS: PHY: Change maintainer to reviewer Florian Fainelli
2015-11-25 1:04 ` Joe Perches
2015-11-25 16:36 ` David Miller
2015-11-25 18:07 ` Florian Fainelli [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=5655F8DD.3000405@gmail.com \
--to=f.fainelli@gmail.com \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.