From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
roopa@nvidia.com, nikolay@nvidia.com, jiri@nvidia.com,
idosch@nvidia.com
Subject: Re: [PATCH net-next 0/5] Code movement to br_switchdev.c
Date: Fri, 29 Oct 2021 03:10:09 +0000 [thread overview]
Message-ID: <163547700904.18853.17271389972838832922.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211027162119.2496321-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 27 Oct 2021 19:21:14 +0300 you wrote:
> This is one more refactoring patch set for the Linux bridge, where more
> logic that is specific to switchdev is moved into br_switchdev.c, which
> is compiled out when CONFIG_NET_SWITCHDEV is disabled.
>
> Vladimir Oltean (5):
> net: bridge: provide shim definition for br_vlan_flags
> net: bridge: move br_vlan_replay to br_switchdev.c
> net: bridge: split out the switchdev portion of br_mdb_notify
> net: bridge: mdb: move all switchdev logic to br_switchdev.c
> net: bridge: switchdev: consistent function naming
>
> [...]
Here is the summary with links:
- [net-next,1/5] net: bridge: provide shim definition for br_vlan_flags
https://git.kernel.org/netdev/net-next/c/c5f6e5ebc2af
- [net-next,2/5] net: bridge: move br_vlan_replay to br_switchdev.c
https://git.kernel.org/netdev/net-next/c/4a6849e46173
- [net-next,3/5] net: bridge: split out the switchdev portion of br_mdb_notify
https://git.kernel.org/netdev/net-next/c/9ae9ff994b0e
- [net-next,4/5] net: bridge: mdb: move all switchdev logic to br_switchdev.c
https://git.kernel.org/netdev/net-next/c/9776457c784f
- [net-next,5/5] net: bridge: switchdev: consistent function naming
https://git.kernel.org/netdev/net-next/c/326b212e9cd6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-10-29 3:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 16:21 [PATCH net-next 0/5] Code movement to br_switchdev.c Vladimir Oltean
2021-10-27 16:21 ` [PATCH net-next 1/5] net: bridge: provide shim definition for br_vlan_flags Vladimir Oltean
2021-10-27 19:28 ` Nikolay Aleksandrov
2021-10-27 19:45 ` Vladimir Oltean
2021-10-27 19:50 ` Nikolay Aleksandrov
2021-10-27 19:54 ` Vladimir Oltean
2021-10-28 8:45 ` Nikolay Aleksandrov
2021-10-27 16:21 ` [PATCH net-next 2/5] net: bridge: move br_vlan_replay to br_switchdev.c Vladimir Oltean
2021-10-28 8:46 ` Nikolay Aleksandrov
2021-10-27 16:21 ` [PATCH net-next 3/5] net: bridge: split out the switchdev portion of br_mdb_notify Vladimir Oltean
2021-10-28 8:48 ` Nikolay Aleksandrov
2021-10-27 16:21 ` [PATCH net-next 4/5] net: bridge: mdb: move all switchdev logic to br_switchdev.c Vladimir Oltean
2021-10-28 8:50 ` Nikolay Aleksandrov
2021-10-27 16:21 ` [PATCH net-next 5/5] net: bridge: switchdev: consistent function naming Vladimir Oltean
2021-10-28 8:50 ` Nikolay Aleksandrov
2021-10-29 3:10 ` patchwork-bot+netdevbpf [this message]
2021-11-01 15:05 ` [PATCH net-next 0/5] Code movement to br_switchdev.c Jiri Pirko
2021-11-02 11:11 ` Vladimir Oltean
2021-11-02 11:49 ` Jiri Pirko
2021-11-02 12:02 ` Vladimir Oltean
2021-11-02 13:44 ` Jiri Pirko
2021-11-02 17:03 ` Andrew Lunn
2021-11-02 17:20 ` Vladimir Oltean
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=163547700904.18853.17271389972838832922.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=roopa@nvidia.com \
--cc=vladimir.oltean@nxp.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.