From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, dsahern@kernel.org,
horms@kernel.org, willemb@google.com
Subject: Re: [PATCH net-next v3 0/3] ipv6: Honor oif when choosing nexthop for locally generated traffic
Date: Sat, 13 Jun 2026 01:00:26 +0000 [thread overview]
Message-ID: <178131242613.1315131.18235073740348361443.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260611154605.992528-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 11 Jun 2026 18:46:02 +0300 you wrote:
> Patch #1 is a preparation patch following the comment from Sashiko on
> v2. See details in the commit message.
>
> Patch #2 aligns IPv6 with IPv4 and changes IPv6 route lookup to prefer a
> nexthop whose nexthop device matches the specified oif.
>
> Patch #3 adds a selftest.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/3] ipv6: Select best matching nexthop object in fib6_table_lookup()
https://git.kernel.org/netdev/net-next/c/484bb9d164df
- [net-next,v3,2/3] ipv6: Honor oif when choosing nexthop for locally generated traffic
https://git.kernel.org/netdev/net-next/c/d25e7e9d8a6c
- [net-next,v3,3/3] selftests: fib_tests: Add test cases for route lookup with oif
https://git.kernel.org/netdev/net-next/c/707c1f866c68
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-06-13 1:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 15:46 [PATCH net-next v3 0/3] ipv6: Honor oif when choosing nexthop for locally generated traffic Ido Schimmel
2026-06-11 15:46 ` [PATCH net-next v3 1/3] ipv6: Select best matching nexthop object in fib6_table_lookup() Ido Schimmel
2026-06-11 18:25 ` David Ahern
2026-06-11 15:46 ` [PATCH net-next v3 2/3] ipv6: Honor oif when choosing nexthop for locally generated traffic Ido Schimmel
2026-06-11 15:46 ` [PATCH net-next v3 3/3] selftests: fib_tests: Add test cases for route lookup with oif Ido Schimmel
2026-06-11 18:28 ` David Ahern
2026-06-13 1:00 ` 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=178131242613.1315131.18235073740348361443.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@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 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.