net: dsa: drop vlan_getnext
The VLAN GetNext operation is specific to some switches, and thus can be complicated to implement for some drivers. Remove the support for the vlan_getnext/port_pvid_get approach in favor of the generic and simpler port_vlan_dump function. Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:

committed by
David S. Miller

parent
ceff5eff3a
commit
477b184526
@@ -542,12 +542,6 @@ Bridge layer
|
||||
Bridge VLAN filtering
|
||||
---------------------
|
||||
|
||||
- port_pvid_get: bridge layer function invoked when a Port-based VLAN ID is
|
||||
queried for the given switch port
|
||||
|
||||
- port_pvid_set: bridge layer function invoked when a Port-based VLAN ID needs
|
||||
to be configured on the given switch port
|
||||
|
||||
- port_vlan_add: bridge layer function invoked when a VLAN is configured
|
||||
(tagged or untagged) for the given switch port
|
||||
|
||||
@@ -558,9 +552,6 @@ Bridge VLAN filtering
|
||||
function that the driver has to call for each VLAN the given port is a member
|
||||
of. A switchdev object is used to carry the VID and bridge flags.
|
||||
|
||||
- vlan_getnext: bridge layer function invoked to query the next configured VLAN
|
||||
in the switch, i.e. returns the bitmaps of members and untagged ports
|
||||
|
||||
- port_fdb_add: bridge layer function invoked when the bridge wants to install a
|
||||
Forwarding Database entry, the switch hardware should be programmed with the
|
||||
specified address in the specified VLAN Id in the forwarding database
|
||||
|
Reference in New Issue
Block a user