From: Jakub Kicinski <kuba@kernel.org>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: patchwork-bot+netdevbpf@kernel.org,
Ido Schimmel <idosch@nvidia.com>,
netdev@vger.kernel.org, davem@davemloft.net, pabeni@redhat.com,
edumazet@google.com, dsahern@kernel.org, horms@kernel.org,
gnault@redhat.com, stfomichev@gmail.com
Subject: Re: [PATCH net 0/2] ipv6: Multipath routing fixes
Date: Fri, 4 Apr 2025 07:49:38 -0700 [thread overview]
Message-ID: <20250404074938.218ac944@kernel.org> (raw)
In-Reply-To: <174377763303.3283451.9282505899516359075.git-patchwork-notify@kernel.org>
On Fri, 04 Apr 2025 14:40:33 +0000 patchwork-bot+netdevbpf@kernel.org
wrote:
> Hello:
>
> This series was applied to netdev/net.git (main)
> by Jakub Kicinski <kuba@kernel.org>:
>
> On Wed, 2 Apr 2025 14:42:22 +0300 you wrote:
> > This patchset contains two fixes for IPv6 multipath routing. See the
> > commit messages for more details.
> >
> > Ido Schimmel (2):
> > ipv6: Start path selection from the first nexthop
> > ipv6: Do not consider link down nexthops in path selection
> >
> > [...]
>
> Here is the summary with links:
> - [net,1/2] ipv6: Start path selection from the first nexthop
> https://git.kernel.org/netdev/net/c/4d0ab3a6885e
> - [net,2/2] ipv6: Do not consider link down nexthops in path selection
> https://git.kernel.org/netdev/net/c/8b8e0dd35716
>
> You are awesome, thank you!
Ugh, rushed this it seems.
Sorry, Willem.
next prev parent reply other threads:[~2025-04-04 14:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 11:42 [PATCH net 0/2] ipv6: Multipath routing fixes Ido Schimmel
2025-04-02 11:42 ` [PATCH net 1/2] ipv6: Start path selection from the first nexthop Ido Schimmel
2025-04-04 14:40 ` Willem de Bruijn
2025-04-06 13:45 ` Ido Schimmel
2025-04-06 18:30 ` Willem de Bruijn
2025-04-07 6:38 ` Ido Schimmel
2025-04-07 14:31 ` Willem de Bruijn
2025-04-02 11:42 ` [PATCH net 2/2] ipv6: Do not consider link down nexthops in path selection Ido Schimmel
2025-04-04 13:22 ` Willem de Bruijn
2025-04-04 14:03 ` Willem de Bruijn
2025-04-04 14:07 ` Willem de Bruijn
2025-04-04 14:40 ` [PATCH net 0/2] ipv6: Multipath routing fixes patchwork-bot+netdevbpf
2025-04-04 14:49 ` Jakub Kicinski [this message]
2025-04-04 16:22 ` Willem de Bruijn
2025-04-07 15:12 ` Guillaume Nault
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=20250404074938.218ac944@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=stfomichev@gmail.com \
--cc=willemdebruijn.kernel@gmail.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.