Searched hist:"920 a33cd72314f4ea96b5224fa8c7d4472d81880" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/net/bridge/ |
| H A D | br_if.c | diff 920a33cd72314f4ea96b5224fa8c7d4472d81880 Fri Aug 19 12:48:14 CDT 2022 Vladimir Oltean <vladimir.oltean@nxp.com> net: bridge: move DSA master bridging restriction to DSA
When DSA gains support for multiple CPU ports in a LAG, it will become
mandatory to monitor the changeupper events for the DSA master.
In fact, there are already some restrictions to be imposed in that area,
namely that a DSA master cannot be a bridge port except in some special
circumstances.
Centralize the restrictions at the level of the DSA layer as a
preliminary step.
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Acked-by: Nikolay Aleksandrov <razor@blackwall.org>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
|
| /openbmc/linux/net/dsa/ |
| H A D | slave.c | diff 920a33cd72314f4ea96b5224fa8c7d4472d81880 Fri Aug 19 12:48:14 CDT 2022 Vladimir Oltean <vladimir.oltean@nxp.com> net: bridge: move DSA master bridging restriction to DSA
When DSA gains support for multiple CPU ports in a LAG, it will become
mandatory to monitor the changeupper events for the DSA master.
In fact, there are already some restrictions to be imposed in that area,
namely that a DSA master cannot be a bridge port except in some special
circumstances.
Centralize the restrictions at the level of the DSA layer as a
preliminary step.
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Acked-by: Nikolay Aleksandrov <razor@blackwall.org>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
|