From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Florian Fainelli <f.fainelli@gmail.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, devicetree@vger.kernel.org,
cernekee@gmail.com, mark.rutland@arm.com, romieu@fr.zoreil.com
Subject: Re: [PATCH net-next v5 10/10] MAINTAINERS: add entry for the Broadcom GENET driver
Date: Sat, 15 Feb 2014 00:37:09 +0300 [thread overview]
Message-ID: <52FE8C85.5070008@cogentembedded.com> (raw)
In-Reply-To: <1392336531-28875-11-git-send-email-f.fainelli@gmail.com>
Hello.
On 02/14/2014 03:08 AM, Florian Fainelli wrote:
> Add myself as a maintainer of the Broadcom GENET driver.
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
[...]
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 091b50e..5a7b3ec 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1845,6 +1845,12 @@ L: netdev@vger.kernel.org
> S: Supported
> F: drivers/net/ethernet/broadcom/b44.*
>
> +BROADCOM GENET ETHERNET DRIVER
> +M: Florian Fainelli <f.fainelli@gmail.com>
> +L: netdev@vger.kernel.org
> +S: Supported
> +F: drivers/net/ethernet/broadcom/genet/
> +
Aren't these entries supposed to be sorted alphabetically? If so, in my
alphabet BNX2 comes before GENET...
> BROADCOM BNX2 GIGABIT ETHERNET DRIVER
> M: Michael Chan <mchan@broadcom.com>
> L: netdev@vger.kernel.org
PS: I'm probably wrong, the entries don't appear to be sorted on the 2nd word...
WBR, Sergei
prev parent reply other threads:[~2014-02-14 21:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 0:08 [PATCH net-next v5 00/10] Support for the Broadcom GENET driver Florian Fainelli
2014-02-14 0:08 ` [PATCH net-next v5 01/10] net: phy: add MoCA PHY type Florian Fainelli
2014-02-14 0:08 ` [PATCH net-next v5 02/10] net: phy: update port type for MoCA PHYs Florian Fainelli
2014-02-14 0:08 ` [PATCH net-next v5 03/10] net: phy: broadcom: extract register definitions Florian Fainelli
2014-02-14 0:08 ` [PATCH net-next v5 04/10] net: phy: add Broadcom BCM7xxx internal PHY driver Florian Fainelli
2014-02-14 0:08 ` [PATCH net-next v5 05/10] net: bcmgenet: add driver definitions and private structure Florian Fainelli
2014-02-14 0:08 ` [PATCH net-next v5 06/10] net: bcmgenet: add main driver file Florian Fainelli
2014-02-14 0:08 ` [PATCH net-next v5 07/10] net: bcmgenet: add MDIO routines Florian Fainelli
[not found] ` <1392336531-28875-1-git-send-email-f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-02-14 0:08 ` [PATCH net-next v5 08/10] net: bcmgenet: hook into the build system Florian Fainelli
2014-02-14 5:29 ` [PATCH net-next v5 00/10] Support for the Broadcom GENET driver David Miller
2014-02-14 7:07 ` Florian Fainelli
2014-02-14 9:19 ` Richard Cochran
2014-02-16 18:34 ` Florian Fainelli
2014-02-18 7:37 ` Richard Cochran
2014-02-14 0:08 ` [PATCH net-next v5 09/10] Documentation: add Device tree bindings for Broadcom GENET Florian Fainelli
2014-02-14 10:19 ` Mark Rutland
2014-02-14 17:36 ` Florian Fainelli
2014-02-17 23:10 ` Sergei Shtylyov
2014-02-17 22:18 ` Florian Fainelli
2014-02-14 0:08 ` [PATCH net-next v5 10/10] MAINTAINERS: add entry for the Broadcom GENET driver Florian Fainelli
2014-02-14 21:37 ` Sergei Shtylyov [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=52FE8C85.5070008@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=cernekee@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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).