From: Florian Fainelli <f.fainelli@gmail.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, afleming@freescale.com, jogo@openwrt.org,
bhutchings@solarflare.com
Subject: Re: [PATCH 0/3 v3] phy: allow flagging PHY devices as internal
Date: Fri, 24 May 2013 22:31:11 +0100 [thread overview]
Message-ID: <201305242231.11632.f.fainelli@gmail.com> (raw)
In-Reply-To: <1369307473-20696-1-git-send-email-f.fainelli@gmail.com>
Ben,
Le jeudi 23 mai 2013 12:11:10, Florian Fainelli a écrit :
> David, Andy,
>
> This small patch set updates libphy to allow PHY drivers to flag a
> specific PHY device as internal, which is then used to accurately
> report the transceiver type (internal vs external) in ethtool.
Does the first patch works for you or you do want me to be more descriptive?
Thanks
>
> As far as I can tell we only have one in-tree driver for the moment
> which is known to be for internal PHYs.
>
> Florian Fainelli (3):
> net: ethtool: disambiguate XCVR_* meaning
> phy: allow drivers to flag a PHY device as internal
> phy: bcm63xx: report Broadcom BCM63xx PHYs as internal
>
> drivers/net/phy/bcm63xx.c | 4 ++--
> drivers/net/phy/phy.c | 3 ++-
> drivers/net/phy/phy_device.c | 3 +++
> include/linux/phy.h | 12 ++++++++++++
> include/uapi/linux/ethtool.h | 4 ++--
> 5 files changed, 21 insertions(+), 5 deletions(-)
--
Florian
next prev parent reply other threads:[~2013-05-24 21:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 11:11 [PATCH 0/3 v3] phy: allow flagging PHY devices as internal Florian Fainelli
2013-05-23 11:11 ` [PATCH 1/3 net-next v3] net: ethtool: disambiguate XCVR_* meaning Florian Fainelli
2013-05-27 16:49 ` Ben Hutchings
2013-05-23 11:11 ` [PATCH 2/3 net-next v3] phy: allow drivers to flag a PHY device as internal Florian Fainelli
2013-05-23 11:11 ` [PATCH 3/3 net-next v3] phy: bcm63xx: report Broadcom BCM63xx PHYs " Florian Fainelli
2013-05-24 21:31 ` Florian Fainelli [this message]
2013-05-26 6:36 ` [PATCH 0/3 v3] phy: allow flagging PHY devices " David Miller
2013-05-28 5:46 ` David Miller
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=201305242231.11632.f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=afleming@freescale.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=jogo@openwrt.org \
--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.