From: Yuya Kusakabe <yuya.kusakabe@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Yuya Kusakabe <yuya.kusakabe@gmail.com>,
David Ahern <dsahern@kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next 0/6] seg6: SRv6 Mobile User Plane (RFC 9433)
Date: Mon, 4 May 2026 10:19:18 +0900 [thread overview]
Message-ID: <20260504011918.1320307-1-yuya.kusakabe@gmail.com> (raw)
In-Reply-To: <20260503140547.6d732f4b@phoenix.local>
On Sun, 03 May 2026 14:05:47 -0700, Stephen Hemminger wrote:
> Automated AI review of iproute2 is not setup yet, but manual run showed:
> ...
> Please fix the invarg() usage throughout the series.
Thanks for running the AI review against this series.
v2 will drop the seg6local_action_check_attrs() helper entirely
instead of fixing the invarg() call sites, matching how every other
seg6local action lets the kernel return EINVAL via netlink extack.
v2 will be posted once the 24-hour repost window has elapsed.
Thanks,
Yuya
prev parent reply other threads:[~2026-05-04 1:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-03 15:30 [PATCH iproute2-next 0/6] seg6: SRv6 Mobile User Plane (RFC 9433) Yuya Kusakabe
2026-05-03 15:30 ` [PATCH iproute2-next 1/6] seg6: add support for the End.MAP behavior Yuya Kusakabe
2026-05-03 15:30 ` [PATCH iproute2-next 2/6] seg6: add support for the End.M.GTP4.E behavior Yuya Kusakabe
2026-05-03 15:30 ` [PATCH iproute2-next 3/6] seg6: add support for the End.M.GTP6.E behavior Yuya Kusakabe
2026-05-03 15:30 ` [PATCH iproute2-next 4/6] seg6: add support for the End.M.GTP6.D behavior Yuya Kusakabe
2026-05-03 15:30 ` [PATCH iproute2-next 5/6] seg6: add support for the End.M.GTP6.D.Di behavior Yuya Kusakabe
2026-05-03 15:30 ` [PATCH iproute2-next 6/6] seg6: add support for the H.M.GTP4.D behavior Yuya Kusakabe
2026-05-03 16:45 ` [PATCH iproute2-next 0/6] seg6: SRv6 Mobile User Plane (RFC 9433) Yuya Kusakabe
2026-05-03 21:05 ` Stephen Hemminger
2026-05-04 1:19 ` Yuya Kusakabe [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=20260504011918.1320307-1-yuya.kusakabe@gmail.com \
--to=yuya.kusakabe@gmail.com \
--cc=dsahern@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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