diff options
| author | Vladimir Oltean <vladimir.oltean@nxp.com> | 2022-02-25 10:22:23 +0100 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2022-02-27 12:06:14 +0100 |
| commit | 06b9cce42634a50f2840777a66553b02320db5ef (patch) | |
| tree | 4ed5ab6bc3f7efe290468c12189575b85f3c2b0a /drivers/net/dsa/dsa_loop.c | |
| parent | net: dsa: request drivers to perform FDB isolation (diff) | |
| download | linux-06b9cce42634a50f2840777a66553b02320db5ef.tar.xz linux-06b9cce42634a50f2840777a66553b02320db5ef.zip | |
net: dsa: pass extack to .port_bridge_join driver methods
As FDB isolation cannot be enforced between VLAN-aware bridges in lack
of hardware assistance like extra FID bits, it seems plausible that many
DSA switches cannot do it. Therefore, they need to reject configurations
with multiple VLAN-aware bridges from the two code paths that can
transition towards that state:
- joining a VLAN-aware bridge
- toggling VLAN awareness on an existing bridge
The .port_vlan_filtering method already propagates the netlink extack to
the driver, let's propagate it from .port_bridge_join too, to make sure
that the driver can use the same function for both.
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/dsa/dsa_loop.c')
| -rw-r--r-- | drivers/net/dsa/dsa_loop.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/drivers/net/dsa/dsa_loop.c b/drivers/net/dsa/dsa_loop.c index 33daaf10c488..263e41191c29 100644 --- a/drivers/net/dsa/dsa_loop.c +++ b/drivers/net/dsa/dsa_loop.c @@ -168,7 +168,8 @@ static int dsa_loop_phy_write(struct dsa_switch *ds, int port, static int dsa_loop_port_bridge_join(struct dsa_switch *ds, int port, struct dsa_bridge bridge, - bool *tx_fwd_offload) + bool *tx_fwd_offload, + struct netlink_ext_ack *extack) { dev_dbg(ds->dev, "%s: port: %d, bridge: %s\n", __func__, port, bridge.dev->name); |