From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
donald.hunter@gmail.com, jacob.e.keller@intel.com,
yuyanghuang@google.com, sdf@fomichev.me, gnault@redhat.com,
nicolas.dichtel@6wind.com, petrm@nvidia.com
Subject: Re: [PATCH net-next v2 00/13] tools: ynl: c: basic netlink-raw support
Date: Fri, 11 Apr 2025 03:30:35 +0000 [thread overview]
Message-ID: <174434223551.3945310.12371352099269592658.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250410014658.782120-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 9 Apr 2025 18:46:45 -0700 you wrote:
> Basic support for netlink-raw AKA classic netlink in user space C codegen.
> This series is enough to read routes and addresses from the kernel
> (see the samples in patches 12 and 13).
>
> Specs need to be slightly adjusted and decorated with the c naming info.
>
> In terms of codegen this series includes just the basic plumbing required
> to skip genlmsghdr and handle request types which may technically also
> be legal in genetlink-legacy but are very uncommon there.
>
> [...]
Here is the summary with links:
- [net-next,v2,01/13] netlink: specs: rename rtnetlink specs in accordance with family name
https://git.kernel.org/netdev/net-next/c/cd5e64fb959a
- [net-next,v2,02/13] netlink: specs: rt-route: specify fixed-header at operations level
https://git.kernel.org/netdev/net-next/c/97a33caa9071
- [net-next,v2,03/13] netlink: specs: rt-addr: remove the fixed members from attrs
https://git.kernel.org/netdev/net-next/c/d460016e7bca
- [net-next,v2,04/13] netlink: specs: rt-route: remove the fixed members from attrs
https://git.kernel.org/netdev/net-next/c/295ff1e95201
- [net-next,v2,05/13] netlink: specs: rt-addr: add C naming info
https://git.kernel.org/netdev/net-next/c/52d062362c05
- [net-next,v2,06/13] netlink: specs: rt-route: add C naming info
https://git.kernel.org/netdev/net-next/c/1652e1f35dfb
- [net-next,v2,07/13] tools: ynl: support creating non-genl sockets
(no matching commit)
- [net-next,v2,08/13] tools: ynl-gen: don't consider requests with fixed hdr empty
https://git.kernel.org/netdev/net-next/c/e0a7903c323f
- [net-next,v2,09/13] tools: ynl: don't use genlmsghdr in classic netlink
https://git.kernel.org/netdev/net-next/c/7e8ba0c7de2b
- [net-next,v2,10/13] tools: ynl-gen: consider dump ops without a do "type-consistent"
https://git.kernel.org/netdev/net-next/c/e8025e72aad6
- [net-next,v2,11/13] tools: ynl-gen: use family c-name in notifications
https://git.kernel.org/netdev/net-next/c/882e7b1365ce
- [net-next,v2,12/13] tools: ynl: generate code for rt-addr and add a sample
(no matching commit)
- [net-next,v2,13/13] tools: ynl: generate code for rt-route and add a sample
(no matching commit)
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:[~2025-04-11 3:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 1:46 [PATCH net-next v2 00/13] tools: ynl: c: basic netlink-raw support Jakub Kicinski
2025-04-10 1:46 ` [PATCH net-next v2 01/13] netlink: specs: rename rtnetlink specs in accordance with family name Jakub Kicinski
2025-04-10 8:52 ` Paolo Abeni
2025-04-10 12:39 ` Donald Hunter
2025-04-11 1:28 ` Jakub Kicinski
2025-04-10 1:46 ` [PATCH net-next v2 02/13] netlink: specs: rt-route: specify fixed-header at operations level Jakub Kicinski
2025-04-10 1:46 ` [PATCH net-next v2 03/13] netlink: specs: rt-addr: remove the fixed members from attrs Jakub Kicinski
2025-04-10 1:46 ` [PATCH net-next v2 04/13] netlink: specs: rt-route: " Jakub Kicinski
2025-04-10 1:46 ` [PATCH net-next v2 05/13] netlink: specs: rt-addr: add C naming info Jakub Kicinski
2025-04-10 1:46 ` [PATCH net-next v2 06/13] netlink: specs: rt-route: " Jakub Kicinski
2025-04-10 1:46 ` [PATCH net-next v2 07/13] tools: ynl: support creating non-genl sockets Jakub Kicinski
2025-04-10 1:46 ` [PATCH net-next v2 08/13] tools: ynl-gen: don't consider requests with fixed hdr empty Jakub Kicinski
2025-04-10 1:46 ` [PATCH net-next v2 09/13] tools: ynl: don't use genlmsghdr in classic netlink Jakub Kicinski
2025-04-10 1:46 ` [PATCH net-next v2 10/13] tools: ynl-gen: consider dump ops without a do "type-consistent" Jakub Kicinski
2025-04-10 1:46 ` [PATCH net-next v2 11/13] tools: ynl-gen: use family c-name in notifications Jakub Kicinski
2025-04-10 1:46 ` [PATCH net-next v2 12/13] tools: ynl: generate code for rt-addr and add a sample Jakub Kicinski
2025-04-18 17:04 ` Kory Maincent
2025-04-18 23:29 ` Jakub Kicinski
2025-04-10 1:46 ` [PATCH net-next v2 13/13] tools: ynl: generate code for rt-route " Jakub Kicinski
2025-04-11 3:30 ` 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=174434223551.3945310.12371352099269592658.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=sdf@fomichev.me \
--cc=yuyanghuang@google.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;
as well as URLs for NNTP newsgroup(s).