From: patchwork-bot+netdevbpf@kernel.org
To: Justin Iurman <justin.iurman@6wind.com>
Cc: netdev@vger.kernel.org, andrea.mayer@uniroma2.it,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, justin.iurman@gmail.com,
nicolas.dichtel@6wind.com, stefano.salsano@uniroma2.it
Subject: Re: [PATCH net-next v5 0/2] Add support for per-route seg6 tunsrc
Date: Fri, 27 Mar 2026 01:50:13 +0000 [thread overview]
Message-ID: <177457621353.3256339.515984783963679850.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260324091434.359341-1-justin.iurman@6wind.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 24 Mar 2026 10:14:32 +0100 you wrote:
> This series adds support for the new per-route seg6 "tunsrc" parameter.
> Selftests are extended to make sure it works as expected.
>
> Example with the iproute2-next companion patch:
>
> ip -6 r a 2001:db8:1::/64 encap seg6 mode encap tunsrc 2001:db8:ab::
> segs 2001:db8:42::1,2001:db8:ffff::2 dev eth0
>
> [...]
Here is the summary with links:
- [net-next,v5,1/2] seg6: add per-route tunnel source address
https://git.kernel.org/netdev/net-next/c/78723a62b969
- [net-next,v5,2/2] selftests: add check for seg6 tunsrc
https://git.kernel.org/netdev/net-next/c/2d047673d374
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-03-27 1:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 9:14 [PATCH net-next v5 0/2] Add support for per-route seg6 tunsrc Justin Iurman
2026-03-24 9:14 ` [PATCH net-next v5 1/2] seg6: add per-route tunnel source address Justin Iurman
2026-03-24 9:14 ` [PATCH net-next v5 2/2] selftests: add check for seg6 tunsrc Justin Iurman
2026-03-25 1:55 ` Andrea Mayer
2026-03-27 1:50 ` 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=177457621353.3256339.515984783963679850.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrea.mayer@uniroma2.it \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=justin.iurman@6wind.com \
--cc=justin.iurman@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=stefano.salsano@uniroma2.it \
/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