summaryrefslogtreecommitdiff
path: root/scripts/lib/kdoc/kdoc_parser.py
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2024-12-20 13:16:46 -0800
committerJakub Kicinski <kuba@kernel.org>2024-12-20 13:16:47 -0800
commitc1bc6d217858f7de7db01658f4b0d799bebc21ac (patch)
tree47d22e55011913428c774c9bc91454e2b4049577 /scripts/lib/kdoc/kdoc_parser.py
parent05dd04b218f42c57a14e330fd8583995f141ed6b (diff)
parentdca12e9ab7603d94e47ded65080f750d6527c852 (diff)
Merge branch 'bridge-handle-changes-in-vlan_flag_bridge_binding'
Petr Machata says: ==================== bridge: Handle changes in VLAN_FLAG_BRIDGE_BINDING When bridge binding is enabled on a VLAN netdevice, its link state should track bridge ports that are members of the corresponding VLAN. This works for a newly-added netdevices. However toggling the option does not have the effect of enabling or disabling the behavior as appropriate. In this patchset, have bridge react to bridge_binding toggles on VLAN uppers. There has been another attempt at supporting this behavior in 2022 by Sevinj Aghayeva [0]. A discussion ensued that informed how this new patchset is constructed, namely that the logic is in the bridge as opposed to the 8021q driver, and the bridge reacts to NETDEV_CHANGE events on the 8021q upper. Patches #1 and #2 contain the implementation, patches #3 and #4 a selftest. [0] https://lore.kernel.org/netdev/cover.1660100506.git.sevinj.aghayeva@gmail.com/ ==================== Link: https://patch.msgid.link/cover.1734540770.git.petrm@nvidia.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_parser.py')
0 files changed, 0 insertions, 0 deletions