From: Philippe Reynes <tremyfr@gmail.com>
To: davem@davemloft.net, decot@googlers.com, f.fainelli@gmail.com,
fugang.duan@nxp.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Philippe Reynes <tremyfr@gmail.com>
Subject: [PATCH 0/3] fec: ethtool: move to new api {get|set}_link_ksettings
Date: Fri, 15 Apr 2016 00:34:58 +0200 [thread overview]
Message-ID: <1460673301-10599-1-git-send-email-tremyfr@gmail.com> (raw)
Ethtool has a new api {get|set}_link_ksettings that deprecate
the old api {get|set}_settings. We update the fec driver to use
this new ethtool api.
For this first version, I've converted old u32 value in phy structure
to link_modes structure. Another way would be to replace u32 in
phy structure to use DECLARE_LINK_MODE_MASK for advertising, ....
Philippe Reynes (3):
net: ethtool: export conversion function between u32 and link mode
phy: add generic function to support ksetting support
fec: move to new ethtool api {get|set}_link_ksettings
drivers/net/ethernet/freescale/fec_main.c | 16 +++---
drivers/net/phy/phy.c | 81 +++++++++++++++++++++++++++++
include/linux/ethtool.h | 7 +++
include/linux/phy.h | 4 ++
net/core/ethtool.c | 21 ++++---
5 files changed, 112 insertions(+), 17 deletions(-)
--
1.7.4.4
next reply other threads:[~2016-04-14 22:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 22:34 Philippe Reynes [this message]
2016-04-14 22:34 ` [PATCH 1/3] net: ethtool: export conversion function between u32 and link mode Philippe Reynes
2016-04-14 22:35 ` [PATCH 2/3] phy: add generic function to support ksetting support Philippe Reynes
2016-04-15 2:50 ` Fugang Duan
2016-04-15 22:53 ` Philippe Reynes
2016-04-14 22:35 ` [PATCH 3/3] fec: move to new ethtool api {get|set}_link_ksettings Philippe Reynes
2016-04-15 2:38 ` Fugang Duan
2016-04-18 18:45 ` [PATCH 0/3] fec: ethtool: move to new " 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=1460673301-10599-1-git-send-email-tremyfr@gmail.com \
--to=tremyfr@gmail.com \
--cc=davem@davemloft.net \
--cc=decot@googlers.com \
--cc=f.fainelli@gmail.com \
--cc=fugang.duan@nxp.com \
--cc=linux-kernel@vger.kernel.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 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).