From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
jiri@resnulli.us, donald.hunter@gmail.com, sdf@google.com,
Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next 0/3] tools: ynl: auto-gen for all genetlink families
Date: Thu, 1 Feb 2024 16:49:23 -0800 [thread overview]
Message-ID: <20240202004926.447803-1-kuba@kernel.org> (raw)
The code gen has caught up with all features required in genetlink
families in Linux 6.8 already. We have also stopped committing auto-
-generated user space code to the tree. Instead of listing all the
families in the Makefile search the spec directory, and generate
code for everything that's not legacy netlink.
Jakub Kicinski (3):
tools: ynl: include dpll and mptcp_pm in C codegen
tools: ynl: generate code for ovs families
tools: ynl: auto-gen for all genetlink families
tools/net/ynl/Makefile.deps | 2 ++
tools/net/ynl/generated/Makefile | 5 ++-
tools/net/ynl/samples/ovs.c | 60 ++++++++++++++++++++++++++++++++
3 files changed, 66 insertions(+), 1 deletion(-)
create mode 100644 tools/net/ynl/samples/ovs.c
--
2.43.0
next reply other threads:[~2024-02-02 0:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 0:49 Jakub Kicinski [this message]
2024-02-02 0:49 ` [PATCH net-next 1/3] tools: ynl: include dpll and mptcp_pm in C codegen Jakub Kicinski
2024-02-02 10:21 ` Jiri Pirko
2024-02-02 0:49 ` [PATCH net-next 2/3] tools: ynl: generate code for ovs families Jakub Kicinski
2024-02-02 10:24 ` Jiri Pirko
2024-02-02 0:49 ` [PATCH net-next 3/3] tools: ynl: auto-gen for all genetlink families Jakub Kicinski
2024-02-02 10:25 ` Jiri Pirko
2024-02-03 5:20 ` [PATCH net-next 0/3] " 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=20240202004926.447803-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@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).