[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <162738120548.32176.11946701736816024763.git-patchwork-notify@kernel.org>
Date: Tue, 27 Jul 2021 10:20:05 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Vladimir Oltean <vladimir.oltean@....com>
Cc: netdev@...r.kernel.org, kuba@...nel.org, davem@...emloft.net,
naresh.kamboju@...aro.org, grygorii.strashko@...com,
lars.povlsen@...rochip.com, Steen.Hegelund@...rochip.com,
UNGLinuxDriver@...rochip.com, f.fainelli@...il.com, andrew@...n.ch,
vivien.didelot@...il.com, idosch@...dia.com, jiri@...dia.com,
roopa@...dia.com, nikolay@...dia.com, lkft@...aro.org
Subject: Re: [PATCH net-next] net: build all switchdev drivers as modules when the
bridge is a module
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Mon, 26 Jul 2021 17:25:36 +0300 you wrote:
> Currently, all drivers depend on the bool CONFIG_NET_SWITCHDEV, but only
> the drivers that call some sort of function exported by the bridge, like
> br_vlan_enabled() or whatever, have an extra dependency on CONFIG_BRIDGE.
>
> Since the blamed commit, all switchdev drivers have a functional
> dependency upon switchdev_bridge_port_{,un}offload(), which is a pair of
> functions exported by the bridge module and not by the bridge-independent
> part of CONFIG_NET_SWITCHDEV.
>
> [...]
Here is the summary with links:
- [net-next] net: build all switchdev drivers as modules when the bridge is a module
https://git.kernel.org/netdev/net-next/c/b0e81817629a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists