From: Heiner Kallweit <hkallweit1@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
David Miller <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [PATCH net-next v2 0/2] net: phy: use generic PHY ability readers if callback get_features isn't set
Date: Wed, 3 Apr 2019 23:13:18 +0200 [thread overview]
Message-ID: <f84950fd-a6cd-205b-a3d2-19ccad9de7d0@gmail.com> (raw)
Meanwhile we have generic functions for reading the abilities of
Clause 22 / 45 PHY's. This allows to use them as fallback in case
callback get_features isn't set. Benefit is the reduction of
boilerplate code in PHY drivers.
v2:
- adjust a comment in patch 1 to match the code
Heiner Kallweit (2):
net: phy: allow a PHY driver to define neither features nor
get_features
net: phy: realtek: remove setting callback get_features and use phylib
default
drivers/net/phy/phy_device.c | 19 ++++++++++++-------
drivers/net/phy/realtek.c | 10 ----------
2 files changed, 12 insertions(+), 17 deletions(-)
--
2.21.0
next reply other threads:[~2019-04-03 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 21:13 Heiner Kallweit [this message]
2019-04-03 21:14 ` [PATCH net-next v2 1/2] net: phy: allow a PHY driver to define neither features nor get_features Heiner Kallweit
2019-04-03 21:25 ` Andrew Lunn
2019-04-03 21:15 ` [PATCH net-next v2 2/2] net: phy: realtek: remove setting callback get_features and use phylib fallback Heiner Kallweit
2019-04-03 21:25 ` Andrew Lunn
2019-04-05 0:55 ` [PATCH net-next v2 0/2] net: phy: use generic PHY ability readers if callback get_features isn't set 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=f84950fd-a6cd-205b-a3d2-19ccad9de7d0@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.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 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).