summaryrefslogtreecommitdiff
path: root/Documentation/i2c
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2016-09-27 07:43:13 -0400
committerDavid S. Miller <davem@davemloft.net>2016-09-27 07:43:56 -0400
commit3783c09eabb78151bcef539ffb16d603b82024f5 (patch)
tree04b4fdb9e56afb26701c0aaca9a30db31a22e77d /Documentation/i2c
parent1955351da41caa1dbf4139191358fed84909d64b (diff)
parentfa92bf04f583dddf275845838e686fd052f5b49a (diff)
Merge branch 'bcmgenet-phydev-revert'
Philippe Reynes says: ==================== net: bcmgenet: only use new api ethtool_{get|set}_link_ksettings Some times ago, a serie of patches were committed : - commit 62469c76007e ("net: ethernet: bcmgenet: use phydev from struct net_device") - commit 6b352ebccbcf ("net: ethernet: broadcom: bcmgenet: use new api ethtool_{get|set}_link_ksettings") The first patch add a regression on this driver, so it should be reverted. As the second patch depend on the former, it should be reverted too. The first patch is buggy because there is a "trick" in this driver. The structure phydev is kept in the private data when the interface go down, and used when the interface go up to enable the phy before the function phy_connect is called. I don't have this hardware, neither the datasheet. So I won't update the driver to avoid this trick. But the real goal of the first serie was to move to the new api ethtool_{get|set}_link_ksettings. So I provide a new version of the patch without the "cleaning" of driver to use the phydev store in the net_device structure. Changelog: v3: - use priv instead of dev (so all the code use the same phydev) v2: - use Florian Fainelli patches for the revert instead of Jaedon Shin - simply use net: bcmgenet: for the prefix of the patch ==================== Acked-by: Florian Fainelli <f.fainelli@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation/i2c')
0 files changed, 0 insertions, 0 deletions