From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, andrew+netdev@lunn.ch,
netdev@vger.kernel.org, idosch@nvidia.com, amcohen@nvidia.com,
mlxsw@nvidia.com
Subject: Re: [PATCH net-next 0/6] mlxsw: Add VXLAN to the same hardware domain as physical bridge ports
Date: Mon, 24 Mar 2025 22:20:33 +0000 [thread overview]
Message-ID: <174285483355.3937.1490840167565257776.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1742224300.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 17 Mar 2025 18:37:25 +0100 you wrote:
> Amit Cohen writes:
>
> Packets which are trapped to CPU for forwarding in software data path
> are handled according to driver marking of skb->offload_{,l3}_fwd_mark.
> Packets which are marked as L2-forwarded in hardware, will not be flooded
> by the bridge to bridge ports which are in the same hardware domain as the
> ingress port.
>
> [...]
Here is the summary with links:
- [net-next,1/6] mlxsw: Trap ARP packets at layer 2 instead of layer 3
https://git.kernel.org/netdev/net-next/c/6d627a29aab8
- [net-next,2/6] mlxsw: spectrum: Call mlxsw_sp_bridge_vxlan_{join, leave}() for VLAN-aware bridge
https://git.kernel.org/netdev/net-next/c/a13fc7ebd994
- [net-next,3/6] mlxsw: spectrum_switchdev: Add an internal API for VXLAN leave
https://git.kernel.org/netdev/net-next/c/413e2c069969
- [net-next,4/6] mlxsw: spectrum_switchdev: Move mlxsw_sp_bridge_vxlan_join()
https://git.kernel.org/netdev/net-next/c/630e7e20d35f
- [net-next,5/6] mlxsw: Add VXLAN bridge ports to same hardware domain as physical bridge ports
https://git.kernel.org/netdev/net-next/c/139ae87714eb
- [net-next,6/6] selftests: vxlan_bridge: Test flood with unresolved FDB entry
https://git.kernel.org/netdev/net-next/c/36ed81bcade9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-03-24 22:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 17:37 [PATCH net-next 0/6] mlxsw: Add VXLAN to the same hardware domain as physical bridge ports Petr Machata
2025-03-17 17:37 ` [PATCH net-next 1/6] mlxsw: Trap ARP packets at layer 2 instead of layer 3 Petr Machata
2025-03-20 15:57 ` Simon Horman
2025-03-17 17:37 ` [PATCH net-next 2/6] mlxsw: spectrum: Call mlxsw_sp_bridge_vxlan_{join, leave}() for VLAN-aware bridge Petr Machata
2025-03-20 15:58 ` Simon Horman
2025-03-17 17:37 ` [PATCH net-next 3/6] mlxsw: spectrum_switchdev: Add an internal API for VXLAN leave Petr Machata
2025-03-20 15:58 ` Simon Horman
2025-03-17 17:37 ` [PATCH net-next 4/6] mlxsw: spectrum_switchdev: Move mlxsw_sp_bridge_vxlan_join() Petr Machata
2025-03-20 15:58 ` Simon Horman
2025-03-17 17:37 ` [PATCH net-next 5/6] mlxsw: Add VXLAN bridge ports to same hardware domain as physical bridge ports Petr Machata
2025-03-20 16:00 ` Simon Horman
2025-03-17 17:37 ` [PATCH net-next 6/6] selftests: vxlan_bridge: Test flood with unresolved FDB entry Petr Machata
2025-03-20 16:00 ` Simon Horman
2025-03-24 22:20 ` 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=174285483355.3937.1490840167565257776.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amcohen@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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.