Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
	f.fainelli@gmail.com, andrew@lunn.ch, vivien.didelot@gmail.com,
	jiri@resnulli.us, idosch@idosch.org, roopa@nvidia.com,
	nikolay@nvidia.com, stephen@networkplumber.org,
	bridge@lists.linux-foundation.org, grygorii.strashko@ti.com,
	arnd@kernel.org
Subject: Re: [PATCH v2 net-next 0/2] Convert switchdev_bridge_port_{,un}offload to notifiers
Date: Wed, 04 Aug 2021 11:40:05 +0000	[thread overview]
Message-ID: <162807720594.23179.2687228457044533864.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210803203409.1274807-1-vladimir.oltean@nxp.com>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Tue,  3 Aug 2021 23:34:07 +0300 you wrote:
> The introduction of the explicit switchdev bridge port offloading API
> has introduced dependency regressions between switchdev drivers and the
> bridge, with some drivers where switchdev support was optional before
> being now compiled as a module when the bridge is a module, or worse.
> 
> This patch makes the switchdev bridge port offload/unoffload events
> visible on the blocking notifier call chain, so that the bridge can
> indirectly do something when those events happen, without the driver
> explicitly calling a symbol exported by the bridge driver.
> 
> [...]

Here is the summary with links:
  - [v2,net-next,1/2] net: make switchdev_bridge_port_{,unoffload} loosely coupled with the bridge
    https://git.kernel.org/netdev/net-next/c/957e2235e526
  - [v2,net-next,2/2] Revert "net: build all switchdev drivers as modules when the bridge is a module"
    https://git.kernel.org/netdev/net-next/c/a54182b2a518

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-08-04 11:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03 20:34 Vladimir Oltean
2021-08-03 20:34 ` [PATCH v2 net-next 1/2] net: make switchdev_bridge_port_{,unoffload} loosely coupled with the bridge Vladimir Oltean
2021-08-03 20:34 ` [PATCH v2 net-next 2/2] Revert "net: build all switchdev drivers as modules when the bridge is a module" Vladimir Oltean
2021-08-03 20:43 ` [PATCH v2 net-next 0/2] Convert switchdev_bridge_port_{,un}offload to notifiers Vladimir Oltean
2021-08-03 23:15   ` Vladimir Oltean
2021-08-04 11:40 ` patchwork-bot+netdevbpf [this message]

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=162807720594.23179.2687228457044533864.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=arnd@kernel.org \
    --cc=bridge@lists.linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=grygorii.strashko@ti.com \
    --cc=idosch@idosch.org \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@nvidia.com \
    --cc=roopa@nvidia.com \
    --cc=stephen@networkplumber.org \
    --cc=vivien.didelot@gmail.com \
    --cc=vladimir.oltean@nxp.com \
    --subject='Re: [PATCH v2 net-next 0/2] Convert switchdev_bridge_port_{,un}offload to notifiers' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).