From: patchwork-bot+netdevbpf@kernel.org
To: Yaroslav Dudkov <aroslavdudkov622@gmail.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org, idosch@nvidia.com,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
weiwan@google.com, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] ipv6: ignore link state in gateway check
Date: Tue, 10 Nov 2026 02:55:01 +0000 [thread overview]
Message-ID: <179427930167.3612825.11874749097898139774.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261104195655.1406837-1-aroslavdudkov622@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 4 Nov 2026 19:56:53 +0000 you wrote:
> IPv6 gateway validation can reject routes in non-main tables when
> ignore_routes_with_linkdown is enabled and the nexthop device has
> no carrier, even though these routes should be added.
>
> Fix this by ignoring link state during gateway validation and add a
> regression selftest covering IPv4 and IPv6 route installation.
>
> [...]
Here is the summary with links:
- [net,v2,1/2] ipv6: ignore link state in gateway check
https://git.kernel.org/netdev/net/c/b76bcf3fff93
- [net,v2,2/2] selftests: fib_tests: Add carrier gateway test
https://git.kernel.org/netdev/net/c/d1b6b27005b4
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:[~2026-11-10 2:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 19:56 Yaroslav Dudkov
2026-11-04 19:56 ` [PATCH net v2 1/2] " Yaroslav Dudkov
2026-11-05 2:12 ` Hangbin Liu
2026-11-04 19:56 ` [PATCH net v2 2/2] selftests: fib_tests: Add carrier gateway test Yaroslav Dudkov
2026-11-05 1:51 ` Hangbin Liu
2026-11-04 20:09 ` [PATCH net v2 0/2] ipv6: ignore link state in gateway check netdev-bot+sinfo
2026-11-08 14:26 ` Ido Schimmel
2026-11-10 2:55 ` 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=179427930167.3612825.11874749097898139774.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aroslavdudkov622@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=weiwan@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®