From: Jakub Kicinski <kuba@kernel•org>
To: Justin Iurman <justin.iurman@gmail•com>
Cc: Justin Iurman <justin.iurman@6wind•com>,
netdev@vger•kernel.org, andrea.mayer@uniroma2•it,
davem@davemloft•net, edumazet@google•com, pabeni@redhat•com,
horms@kernel•org, nicolas.dichtel@6wind•com,
stefano.salsano@uniroma2•it, paolo.lungaroni@uniroma2•it,
ahabdels@cisco•com
Subject: Re: [PATCH net-next v3 0/2] Add support for seg6 tunsrc
Date: Mon, 16 Mar 2026 17:15:04 -0700 [thread overview]
Message-ID: <20260316171504.606024d9@kernel.org> (raw)
In-Reply-To: <1b749c77-3ec6-4821-b4c2-5e8c3ab3033a@gmail.com>
On Mon, 16 Mar 2026 21:01:25 +0100 Justin Iurman wrote:
> > include/uapi/linux/seg6_iptunnel.h | 1 +
> > net/ipv6/seg6_iptunnel.c | 114 +++++++++++++-----
> > .../net/srv6_hencap_red_l3vpn_test.sh | 65 +++++++---
> > 3 files changed, 134 insertions(+), 46 deletions(-)
>
> Looks like patchwork considered that this series has been superseded by
> the companion series for iproute2-next :-(
It's kernel.org's pw-bot not patchwork itself FWIW.
I revived the series. Let's see if the bot discards it again.
If it does you'll have to repost with a different title cause
our CI needs to see it "active" in patchwork to run tests.
prev parent reply other threads:[~2026-03-17 0:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 16:29 [PATCH net-next v3 0/2] Add support for seg6 tunsrc Justin Iurman
2026-03-16 16:29 ` [PATCH net-next v3 1/2] seg6: add per-route tunnel source address Justin Iurman
2026-03-16 16:29 ` [PATCH net-next v3 2/2] selftests: add check for seg6 tunsrc Justin Iurman
2026-03-17 10:54 ` Andrea Mayer
2026-03-17 22:07 ` Jakub Kicinski
2026-03-18 12:29 ` Justin Iurman
2026-03-19 3:50 ` Andrea Mayer
2026-03-16 20:01 ` [PATCH net-next v3 0/2] Add support " Justin Iurman
2026-03-17 0:15 ` Jakub Kicinski [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=20260316171504.606024d9@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=ahabdels@cisco$(echo .)com \
--cc=andrea.mayer@uniroma2$(echo .)it \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=justin.iurman@6wind$(echo .)com \
--cc=justin.iurman@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nicolas.dichtel@6wind$(echo .)com \
--cc=pabeni@redhat$(echo .)com \
--cc=paolo.lungaroni@uniroma2$(echo .)it \
--cc=stefano.salsano@uniroma2$(echo .)it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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