Re: [PATCH RFC iproute2-next v3 2/2] seg6: add support for the End.MAP behavior under seg6mobile encap

[Yuya Kusakabe <yuya.kusakabe@gmail.com>]

On Wed, 17 Sep 2026 17:01:54 -0700
Stephen Hemminger <stephen@networkplumber.org> wrote:

> Please make the three agree. Since End.MAP is meaningless without a
> mapped SID, I would keep the usage string as-is and follow seg6local's
> convention in the man page, which spells the parameter as part of the
> action description rather than as an optional token.
Will do in v4: the synopsis drops the "[ SEG6_MOBILE_PARAM ]" token,
which leaves the action list as the only place that names it.

> 	if (action == SEG6_MOBILE_ACTION_END_MAP && !mapped_sid_ok) {
> 		fprintf(stderr, "Missing mapped_sid for End.MAP\n");
> 		exit(-1);
> 	}
Will add it as written.

> iproute2-next takes uapi header syncs from accepted kernel commits, so
> this cannot be applied until the kernel patches land in net-next.
> Please cite the upstream commit id in 1/2's changelog when you repost.
Understood.  This stays an RFC until the kernel side is in net-next,
and the non-RFC repost will carry the commit id.

Thanks for the review.

Yuya