From: David Ahern <dsahern@kernel.org>
To: Yuya Kusakabe <yuya.kusakabe@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next v2 0/6] seg6: SRv6 Mobile User Plane (RFC 9433)
Date: Wed, 13 May 2026 19:17:53 -0600 [thread overview]
Message-ID: <89e9f18f-2fc9-4453-bcdd-96fe31c0a3aa@kernel.org> (raw)
In-Reply-To: <20260505-seg6-mobile-v2-0-93291b7b0134@gmail.com>
On 5/4/26 10:10 AM, Yuya Kusakabe wrote:
> include/uapi/linux/seg6_local.h | 17 +++++
> ip/iproute.c | 9 ++-
> ip/iproute_lwtunnel.c | 149 +++++++++++++++++++++++++++++++++++++-
> man/man8/ip-route.8.in | 154 ++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 326 insertions(+), 3 deletions(-)
> ---
I am not cc'ed on the netdev patches, so I have no idea the current status.
Future iproute2 patch sets need to have all uapi changes as a standalone
patch that I can drop when applying the rest. Headers are synced from
the kernel.
next prev parent reply other threads:[~2026-05-14 1:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 16:10 [PATCH iproute2-next v2 0/6] seg6: SRv6 Mobile User Plane (RFC 9433) Yuya Kusakabe
2026-05-04 16:10 ` [PATCH iproute2-next v2 1/6] seg6: add support for the End.MAP behavior Yuya Kusakabe
2026-05-04 16:10 ` [PATCH iproute2-next v2 2/6] seg6: add support for the End.M.GTP4.E behavior Yuya Kusakabe
2026-05-04 16:10 ` [PATCH iproute2-next v2 3/6] seg6: add support for the End.M.GTP6.E behavior Yuya Kusakabe
2026-05-04 16:10 ` [PATCH iproute2-next v2 4/6] seg6: add support for the End.M.GTP6.D behavior Yuya Kusakabe
2026-05-04 16:10 ` [PATCH iproute2-next v2 5/6] seg6: add support for the End.M.GTP6.D.Di behavior Yuya Kusakabe
2026-05-04 16:10 ` [PATCH iproute2-next v2 6/6] seg6: add support for the H.M.GTP4.D behavior Yuya Kusakabe
2026-05-14 1:17 ` David Ahern [this message]
2026-05-14 2:31 ` [PATCH iproute2-next v2 0/6] seg6: SRv6 Mobile User Plane (RFC 9433) Yuya Kusakabe
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=89e9f18f-2fc9-4453-bcdd-96fe31c0a3aa@kernel.org \
--to=dsahern@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yuya.kusakabe@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox