From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Ido Schimmel <idosch@nvidia.com>, Petr Machata <petrm@nvidia.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
UNGLinuxDriver@microchip.com,
Lars Povlsen <lars.povlsen@microchip.com>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Karsten Graul <kgraul@linux.ibm.com>,
linux-omap@vger.kernel.org
Subject: [PATCH net-next 0/5] Remove BRENTRY checks from switchdev drivers
Date: Wed, 16 Feb 2022 18:47:47 +0200 [thread overview]
Message-ID: <20220216164752.2794456-1-vladimir.oltean@nxp.com> (raw)
As discussed here:
https://patchwork.kernel.org/project/netdevbpf/patch/20220214233111.1586715-2-vladimir.oltean@nxp.com/#24738869
no switchdev driver makes use of VLAN port objects that lack the
BRIDGE_VLAN_INFO_BRENTRY flag. Notifying them in the first place rather
seems like an omission of commit 9c86ce2c1ae3 ("net: bridge: Notify
about bridge VLANs").
Since commit 3116ad0696dd ("net: bridge: vlan: don't notify to switchdev
master VLANs without BRENTRY flag") that was just merged, the bridge no
longer notifies switchdev upon creation of these VLANs, so we can remove
the checks from drivers.
Vladimir Oltean (5):
mlxsw: spectrum: remove guards against !BRIDGE_VLAN_INFO_BRENTRY
net: lan966x: remove guards against !BRIDGE_VLAN_INFO_BRENTRY
net: sparx5: remove guards against !BRIDGE_VLAN_INFO_BRENTRY
net: ti: am65-cpsw-nuss: remove guards against
!BRIDGE_VLAN_INFO_BRENTRY
net: ti: cpsw: remove guards against !BRIDGE_VLAN_INFO_BRENTRY
drivers/net/ethernet/mellanox/mlxsw/spectrum_span.c | 4 +---
.../net/ethernet/mellanox/mlxsw/spectrum_switchdev.c | 3 +--
.../ethernet/microchip/lan966x/lan966x_switchdev.c | 12 ------------
.../net/ethernet/microchip/sparx5/sparx5_switchdev.c | 10 ++++------
drivers/net/ethernet/ti/am65-cpsw-switchdev.c | 4 ----
drivers/net/ethernet/ti/cpsw_switchdev.c | 4 ----
6 files changed, 6 insertions(+), 31 deletions(-)
--
2.25.1
next reply other threads:[~2022-02-16 16:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 16:47 Vladimir Oltean [this message]
2022-02-16 16:47 ` [PATCH net-next 1/5] mlxsw: spectrum: remove guards against !BRIDGE_VLAN_INFO_BRENTRY Vladimir Oltean
2022-02-16 21:31 ` Ido Schimmel
2022-02-16 16:47 ` [PATCH net-next 2/5] net: lan966x: " Vladimir Oltean
2022-02-16 22:54 ` Horatiu Vultur
2022-02-16 16:47 ` [PATCH net-next 3/5] net: sparx5: " Vladimir Oltean
2022-02-16 16:47 ` [PATCH net-next 4/5] net: ti: am65-cpsw-nuss: " Vladimir Oltean
2022-02-16 16:47 ` [PATCH net-next 5/5] net: ti: cpsw: " Vladimir Oltean
2022-02-16 20:25 ` [PATCH net-next 0/5] Remove BRENTRY checks from switchdev drivers Nikolay Aleksandrov
2022-02-16 20:42 ` Vladimir Oltean
2022-02-17 14:30 ` patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220216164752.2794456-1-vladimir.oltean@nxp.com \
--to=vladimir.oltean@nxp.com \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=grygorii.strashko@ti.com \
--cc=horatiu.vultur@microchip.com \
--cc=idosch@nvidia.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.