| /openbmc/linux/drivers/net/dsa/ |
| H A D | mt7530.c | diff f8b8b1cd5aadd221742b45eb0ee3c8a80abf036a Mon Oct 16 10:12:18 CDT 2017 Vivien Didelot <vivien.didelot@savoirfairelinux.com> net: dsa: split dsa_port's netdev member
The dsa_port structure has a "netdev" member, which can be used for
either the master device, or the slave device, depending on its type.
It is true that today, CPU port are not exposed to userspace, thus the
port's netdev member can be used to point to its master interface.
But it is still slightly confusing, so split it into more explicit
"master" and "slave" members inside an anonymous union.
Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| H A D | bcm_sf2.c | diff f8b8b1cd5aadd221742b45eb0ee3c8a80abf036a Mon Oct 16 10:12:18 CDT 2017 Vivien Didelot <vivien.didelot@savoirfairelinux.com> net: dsa: split dsa_port's netdev member
The dsa_port structure has a "netdev" member, which can be used for
either the master device, or the slave device, depending on its type.
It is true that today, CPU port are not exposed to userspace, thus the
port's netdev member can be used to point to its master interface.
But it is still slightly confusing, so split it into more explicit
"master" and "slave" members inside an anonymous union.
Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/net/dsa/ |
| H A D | dsa.c | diff f8b8b1cd5aadd221742b45eb0ee3c8a80abf036a Mon Oct 16 10:12:18 CDT 2017 Vivien Didelot <vivien.didelot@savoirfairelinux.com> net: dsa: split dsa_port's netdev member
The dsa_port structure has a "netdev" member, which can be used for
either the master device, or the slave device, depending on its type.
It is true that today, CPU port are not exposed to userspace, thus the
port's netdev member can be used to point to its master interface.
But it is still slightly confusing, so split it into more explicit
"master" and "slave" members inside an anonymous union.
Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| H A D | slave.c | diff f8b8b1cd5aadd221742b45eb0ee3c8a80abf036a Mon Oct 16 10:12:18 CDT 2017 Vivien Didelot <vivien.didelot@savoirfairelinux.com> net: dsa: split dsa_port's netdev member
The dsa_port structure has a "netdev" member, which can be used for
either the master device, or the slave device, depending on its type.
It is true that today, CPU port are not exposed to userspace, thus the
port's netdev member can be used to point to its master interface.
But it is still slightly confusing, so split it into more explicit
"master" and "slave" members inside an anonymous union.
Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/include/net/ |
| H A D | dsa.h | diff f8b8b1cd5aadd221742b45eb0ee3c8a80abf036a Mon Oct 16 10:12:18 CDT 2017 Vivien Didelot <vivien.didelot@savoirfairelinux.com> net: dsa: split dsa_port's netdev member
The dsa_port structure has a "netdev" member, which can be used for
either the master device, or the slave device, depending on its type.
It is true that today, CPU port are not exposed to userspace, thus the
port's netdev member can be used to point to its master interface.
But it is still slightly confusing, so split it into more explicit
"master" and "slave" members inside an anonymous union.
Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/drivers/net/dsa/mv88e6xxx/ |
| H A D | chip.c | diff f8b8b1cd5aadd221742b45eb0ee3c8a80abf036a Mon Oct 16 10:12:18 CDT 2017 Vivien Didelot <vivien.didelot@savoirfairelinux.com> net: dsa: split dsa_port's netdev member
The dsa_port structure has a "netdev" member, which can be used for
either the master device, or the slave device, depending on its type.
It is true that today, CPU port are not exposed to userspace, thus the
port's netdev member can be used to point to its master interface.
But it is still slightly confusing, so split it into more explicit
"master" and "slave" members inside an anonymous union.
Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|