From: Jakub Kicinski <kuba@kernel•org>
To: davem@davemloft•net
Cc: netdev@vger•kernel.org, edumazet@google•com, pabeni@redhat•com,
jiri@resnulli•us, Jakub Kicinski <kuba@kernel•org>
Subject: [PATCH net-next 00/11] tools: ynl: generate code for the devlink family
Date: Wed, 7 Jun 2023 13:23:52 -0700 [thread overview]
Message-ID: <20230607202403.1089925-1-kuba@kernel.org> (raw)
Another chunk of changes to support more capabilities in the YNL
code gen. Devlink brings in deep nesting and directional messages
(requests and responses have different IDs). We need a healthy
dose of codegen changes to support those (I wasn't planning to
support code gen for "directional" families initially, but
the importance of devlink and ethtool is undeniable).
I have 1 more series like this (ethtool support).
Jakub Kicinski (11):
netlink: specs: devlink: fill in some details important for C
tools: ynl-gen: use enum names in op strmap more carefully
tools: ynl-gen: refactor strmap helper generation
tools: ynl-gen: enable code gen for directional specs
tools: ynl-gen: try to sort the types more intelligently
tools: ynl-gen: inherit struct use info
tools: ynl-gen: walk nested types in depth
tools: ynl-gen: don't generate forward declarations for policies
tools: ynl-gen: don't generate forward declarations for policies -
regen
tools: ynl: generate code for the devlink family
tools: ynl: add sample for devlink
Documentation/netlink/specs/devlink.yaml | 8 +
tools/net/ynl/generated/Makefile | 2 +-
tools/net/ynl/generated/devlink-user.c | 721 +++++++++++++++++++++++
tools/net/ynl/generated/devlink-user.h | 210 +++++++
tools/net/ynl/generated/fou-user.c | 3 -
tools/net/ynl/generated/handshake-user.c | 4 -
tools/net/ynl/generated/netdev-user.c | 2 -
tools/net/ynl/lib/nlspec.py | 11 +-
tools/net/ynl/samples/.gitignore | 1 +
tools/net/ynl/samples/devlink.c | 60 ++
tools/net/ynl/ynl-gen-c.py | 137 +++--
11 files changed, 1101 insertions(+), 58 deletions(-)
create mode 100644 tools/net/ynl/generated/devlink-user.c
create mode 100644 tools/net/ynl/generated/devlink-user.h
create mode 100644 tools/net/ynl/samples/devlink.c
--
2.40.1
next reply other threads:[~2023-06-07 20:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 20:23 Jakub Kicinski [this message]
2023-06-07 20:23 ` [PATCH net-next 01/11] netlink: specs: devlink: fill in some details important for C Jakub Kicinski
2023-06-07 20:23 ` [PATCH net-next 02/11] tools: ynl-gen: use enum names in op strmap more carefully Jakub Kicinski
2023-06-07 20:23 ` [PATCH net-next 03/11] tools: ynl-gen: refactor strmap helper generation Jakub Kicinski
2023-06-07 20:23 ` [PATCH net-next 04/11] tools: ynl-gen: enable code gen for directional specs Jakub Kicinski
2023-06-07 20:23 ` [PATCH net-next 05/11] tools: ynl-gen: try to sort the types more intelligently Jakub Kicinski
2023-06-07 20:23 ` [PATCH net-next 06/11] tools: ynl-gen: inherit struct use info Jakub Kicinski
2023-06-07 20:23 ` [PATCH net-next 07/11] tools: ynl-gen: walk nested types in depth Jakub Kicinski
2023-06-07 20:24 ` [PATCH net-next 08/11] tools: ynl-gen: don't generate forward declarations for policies Jakub Kicinski
2023-06-07 20:24 ` [PATCH net-next 09/11] tools: ynl-gen: don't generate forward declarations for policies - regen Jakub Kicinski
2023-06-07 20:24 ` [PATCH net-next 10/11] tools: ynl: generate code for the devlink family Jakub Kicinski
2023-06-08 11:48 ` Simon Horman
2023-06-08 15:53 ` Jakub Kicinski
2023-06-09 7:46 ` Simon Horman
2023-06-07 20:24 ` [PATCH net-next 11/11] tools: ynl: add sample for devlink Jakub Kicinski
2023-06-08 21:10 ` [PATCH net-next 00/11] tools: ynl: generate code for the devlink family patchwork-bot+netdevbpf
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=20230607202403.1089925-1-kuba@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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