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, netdev@vger.kernel.org,
idosch@nvidia.com, mlxsw@nvidia.com, andrew+netdev@lunn.ch,
razor@blackwall.org, roopa@nvidia.com, menglong8.dong@gmail.com,
gnault@redhat.com
Subject: Re: [PATCH net-next v2 0/5] vxlan: Join / leave MC group when reconfigured
Date: Tue, 18 Feb 2025 12:10:32 +0000 [thread overview]
Message-ID: <173988063254.4063928.14621964134002219718.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1739548836.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 14 Feb 2025 17:18:19 +0100 you wrote:
> When a vxlan netdevice is brought up, if its default remote is a multicast
> address, the device joins the indicated group.
>
> Therefore when the multicast remote address changes, the device should
> leave the current group and subscribe to the new one. Similarly when the
> interface used for endpoint communication is changed in a situation when
> multicast remote is configured. This is currently not done.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/5] vxlan: Drop 'changelink' parameter from vxlan_dev_configure()
https://git.kernel.org/netdev/net-next/c/5afb1596b90c
- [net-next,v2,2/5] vxlan: Join / leave MC group after remote changes
https://git.kernel.org/netdev/net-next/c/d42d54336834
- [net-next,v2,3/5] selftests: forwarding: lib: Move require_command to net, generalize
https://git.kernel.org/netdev/net-next/c/f802f172d78b
- [net-next,v2,4/5] selftests: test_vxlan_fdb_changelink: Convert to lib.sh
https://git.kernel.org/netdev/net-next/c/24adf47ea9ac
- [net-next,v2,5/5] selftests: test_vxlan_fdb_changelink: Add a test for MC remote change
https://git.kernel.org/netdev/net-next/c/eae1e92a1d41
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-02-18 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 16:18 [PATCH net-next v2 0/5] vxlan: Join / leave MC group when reconfigured Petr Machata
2025-02-14 16:18 ` [PATCH net-next v2 1/5] vxlan: Drop 'changelink' parameter from vxlan_dev_configure() Petr Machata
2025-02-14 16:18 ` [PATCH net-next v2 2/5] vxlan: Join / leave MC group after remote changes Petr Machata
2025-02-14 16:18 ` [PATCH net-next v2 3/5] selftests: forwarding: lib: Move require_command to net, generalize Petr Machata
2025-02-14 16:18 ` [PATCH net-next v2 4/5] selftests: test_vxlan_fdb_changelink: Convert to lib.sh Petr Machata
2025-02-14 16:18 ` [PATCH net-next v2 5/5] selftests: test_vxlan_fdb_changelink: Add a test for MC remote change Petr Machata
2025-02-16 15:10 ` [PATCH net-next v2 0/5] vxlan: Join / leave MC group when reconfigured Nikolay Aleksandrov
2025-02-18 12:10 ` 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=173988063254.4063928.14621964134002219718.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=menglong8.dong@gmail.com \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=roopa@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.