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, andrew+netdev@lunn.ch, netdev@vger.kernel.org,
horms@kernel.org, idosch@nvidia.com, jiri@resnulli.us,
mlxsw@nvidia.com
Subject: Re: [PATCH net v2 0/2] mlxsw: spectrum: Forward packets with an IPv4 link-local source IP
Date: Fri, 15 Aug 2025 18:09:10 +0000 [thread overview]
Message-ID: <175528135025.1165776.2187573508561513859.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1755174341.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 14 Aug 2025 15:06:39 +0200 you wrote:
> By default, Spectrum devices do not forward IPv4 packets with a link-local
> source IP (i.e., 169.254.0.0/16). This behavior does not align with the
> kernel which does forward them. Fix the issue and add a selftest.
>
> v2:
> - Patch #2: disable rp_filter to prevent packets from getting dropped
> on ingress.
>
> [...]
Here is the summary with links:
- [net,v2,1/2] mlxsw: spectrum: Forward packets with an IPv4 link-local source IP
https://git.kernel.org/netdev/net/c/f604d3aaf64f
- [net,v2,2/2] selftest: forwarding: router: Add a test case for IPv4 link-local source IP
https://git.kernel.org/netdev/net/c/5e0b2177bdba
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-08-15 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 13:06 [PATCH net v2 0/2] mlxsw: spectrum: Forward packets with an IPv4 link-local source IP Petr Machata
2025-08-14 13:06 ` [PATCH net v2 1/2] " Petr Machata
2025-08-14 13:06 ` [PATCH net v2 2/2] selftest: forwarding: router: Add a test case for " Petr Machata
2025-08-15 18:09 ` 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=175528135025.1165776.2187573508561513859.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=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jiri@resnulli.us \
--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.