diff options
| author | Florian Fainelli <f.fainelli@gmail.com> | 2019-05-13 14:06:24 -0700 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2019-05-14 15:20:11 -0700 |
| commit | 0fe9f173d6cda95874edeb413b1fa9907b5ae830 (patch) | |
| tree | 224fa5166e59408cd1c0378495a5924de34063eb /MAINTAINERS | |
| parent | cd736d8b67fb22a85a68c1ee8020eb0d660615ec (diff) | |
net: Always descend into dsa/
Jiri reported that with a kernel built with CONFIG_FIXED_PHY=y,
CONFIG_NET_DSA=m and CONFIG_NET_DSA_LOOP=m, we would not get to a
functional state where the mock-up driver is registered. Turns out that
we are not descending into drivers/net/dsa/ unconditionally, and we
won't be able to link-in dsa_loop_bdinfo.o which does the actual mock-up
mdio device registration.
Reported-by: Jiri Pirko <jiri@resnulli.us>
Fixes: 40013ff20b1b ("net: dsa: Fix functional dsa-loop dependency on FIXED_PHY")
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Reviewed-by: Vivien Didelot <vivien.didelot@gmail.com>
Tested-by: Jiri Pirko <jiri@resnulli.us>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions