summaryrefslogtreecommitdiffstats
path: root/lib/test_rhashtable.c
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2015-04-03 15:08:20 -0400
committerDavid S. Miller <davem@davemloft.net>2015-04-03 15:08:20 -0400
commitb98d8075e65c9cb688e73b941d873986e7bbf7ae (patch)
tree11065a9cf7570f455b747eab454dfc9b48916175 /lib/test_rhashtable.c
parentbcad57182425426dd4aa14deb27f97acb329f3cd (diff)
parent898b2970e2c91e4543b579998922822894325866 (diff)
downloadlinux-b98d8075e65c9cb688e73b941d873986e7bbf7ae.tar.gz
linux-b98d8075e65c9cb688e73b941d873986e7bbf7ae.tar.bz2
linux-b98d8075e65c9cb688e73b941d873986e7bbf7ae.zip
Merge branch 'mvneta-sgmii'
Stas Sergeev says: ==================== mvneta: SGMII-based in-band link state signaling Currently the fixed-link DT binding is pre-configured and cannot be changed in run-time. This means the cable unplug events are not being detected, and the link parameters can't be negotiated. The following patches are needed when mvneta is used in fixed-link mode (without MDIO). They add an API to fixed_phy that allows to update status, and use that API in the mvneta driver when parsing the SGMII in-band status. There is also another implementation that doesn't add any API and does everything in mvneta driver locally: https://lkml.org/lkml/2015/3/31/327 I'll let people decide which approach is better. No strong opinion on my side. ==================== Signed-off-by: Stas Sergeev <stsp@users.sourceforge.net> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'lib/test_rhashtable.c')
0 files changed, 0 insertions, 0 deletions