From: patchwork-bot+netdevbpf@kernel.org
To: Hangbin Liu <hangbin.liu@linux.dev>
Cc: dsahern@kernel.org, idosch@nvidia.com, davem@davemloft.net,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
donald.hunter@gmail.com, edumazet@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, liuhangbin@kylinos.cn
Subject: Re: [PATCH net-next v4 0/6] netlink: add lwtunnel encap sub-message support to rt-route
Date: Fri, 16 Oct 2026 00:10:09 +0000 [thread overview]
Message-ID: <179210940926.4168191.14040928625419046386.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261008-ynl_rt_encap-v4-0-4ed2ccf7f949@kylinos.cn>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 08 Oct 2026 16:24:00 +0800 you wrote:
> This series adds YNL sub-message support for lwtunnel encap data in
> the rt-route netlink family, and describes the tunnel-specific
> attribute sets that were previously opaque binary blobs.
>
> The kernel currently emits encap_type after the encap payload nest,
> but YNL sub-message parsing needs the selector (encap_type) first to
> dispatch on the correct attribute set. Patch 1 reorders the kernel
> output, and patch 2 teaches the YNL C code generator to convert enum
> selectors to their string form for sub-message dispatch.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/6] net: lwtunnel: change encap fill order
https://git.kernel.org/netdev/net-next/c/499f32f0eb56
- [net-next,v4,2/6] tools: ynl: convert enum selector to string for sub-message parsing
https://git.kernel.org/netdev/net-next/c/05d3030eff5b
- [net-next,v4,3/6] netlink: specs: rt-route: add lwtunnel encap sub-message support
https://git.kernel.org/netdev/net-next/c/24d11a55860b
- [net-next,v4,4/6] netlink: specs: rt-route: describe lwtunnel IP options
https://git.kernel.org/netdev/net-next/c/e32b5eb4f237
- [net-next,v4,5/6] netlink: specs: rt-route: describe lwt BPF program options
https://git.kernel.org/netdev/net-next/c/8ab5eb3bf6e0
- [net-next,v4,6/6] netlink: specs: rt-route: describe seg6-local attrs
https://git.kernel.org/netdev/net-next/c/5f9d4edccf0c
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-10-16 0:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 8:24 [PATCH net-next v4 0/6] netlink: add lwtunnel encap sub-message support to rt-route Hangbin Liu
2026-10-08 8:24 ` [PATCH net-next v4 1/6] net: lwtunnel: change encap fill order Hangbin Liu
2026-10-08 8:24 ` [PATCH net-next v4 2/6] tools: ynl: convert enum selector to string for sub-message parsing Hangbin Liu
2026-10-09 9:06 ` netdev-bot+sashiko
2026-10-09 9:40 ` Hangbin Liu
2026-10-08 8:24 ` [PATCH net-next v4 3/6] netlink: specs: rt-route: add lwtunnel encap sub-message support Hangbin Liu
2026-10-09 9:06 ` netdev-bot+sashiko
2026-10-08 8:24 ` [PATCH net-next v4 4/6] netlink: specs: rt-route: describe lwtunnel IP options Hangbin Liu
2026-10-09 9:07 ` netdev-bot+sashiko
2026-10-09 9:44 ` Hangbin Liu
2026-10-08 8:24 ` [PATCH net-next v4 5/6] netlink: specs: rt-route: describe lwt BPF program options Hangbin Liu
2026-10-08 8:24 ` [PATCH net-next v4 6/6] netlink: specs: rt-route: describe seg6-local attrs Hangbin Liu
2026-10-09 9:07 ` netdev-bot+sashiko
2026-10-16 0:10 ` 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=179210940926.4168191.14040928625419046386.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=hangbin.liu@linux.dev \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@kylinos.cn \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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