From: Jakub Kicinski <kuba@kernel.org>
To: "Asbjørn Sloth Tønnesen" <ast@fiberby.net>
Cc: netdev@vger.kernel.org, Donald Hunter <donald.hunter@gmail.com>,
Danielle Ratson <danieller@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Greg Thelen <gthelen@google.com>,
Ilya Maximets <i.maximets@ovn.org>,
"Matthieu Baerts (Netdev Foundation)" <matttbe@kernel.org>,
"Maxime Chevallier (Netdev Foundation)"
<maxime.chevallier@bootlin.com>, Paolo Abeni <pabeni@redhat.com>,
"Remy D. Farley" <one-d-wide@protonmail.com>,
Simon Horman <horms@kernel.org>,
Stanislav Fomichev <sdf.kernel@gmail.com>,
Heng Guo <heng.guo@windriver.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH net-next 3/8] tools: ynl: add C-based YNL linter
Date: Thu, 10 Sep 2026 19:33:48 -0700 [thread overview]
Message-ID: <20260910193348.2ded41aa@kernel.org> (raw)
In-Reply-To: <20260910221733.1021864-4-ast@fiberby.net>
On Thu, 10 Sep 2026 22:17:23 +0000 Asbjørn Sloth Tønnesen wrote:
> Validate that structures described in YNL match their C counterpart,
> currently focused on enums.
I don't see the point of this. LLMs will catch most of the problems
and for the hundredth time classic netlink is not the focus for YNL.
Anything genetlink can have YNL generate the code and uAPI so problems
do no exist.
Feel free to keep the code OOT and let's see if you can prove my
assertion wrong within a couple of release :)
If you have any ready fixes to the spec please post them.
I'm also sitting on a bunch of fixes based on LLM scans, I'm just
blocked on the "15 outstanding patches" limit :(
next prev parent reply other threads:[~2026-09-11 2:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 22:17 [RFC PATCH net-next 0/8] tools: ynl: C-based YNL linter Asbjørn Sloth Tønnesen
2026-09-10 22:17 ` [RFC PATCH net-next 1/8] netlink: specs: nftables: add uapi-header Asbjørn Sloth Tønnesen
2026-09-10 22:17 ` [RFC PATCH net-next 2/8] netlink: specs: conntrack: " Asbjørn Sloth Tønnesen
2026-09-11 2:35 ` Jakub Kicinski
2026-09-10 22:17 ` [RFC PATCH net-next 3/8] tools: ynl: add C-based YNL linter Asbjørn Sloth Tønnesen
2026-09-11 2:33 ` Jakub Kicinski [this message]
2026-09-11 22:27 ` Asbjørn Sloth Tønnesen
2026-09-10 22:17 ` [RFC PATCH net-next 4/8] netlink: specs: rt-link: add C naming info Asbjørn Sloth Tønnesen
2026-09-10 22:17 ` [RFC PATCH net-next 5/8] netlink: specs: rt-link: re-align IPv4 devconf Asbjørn Sloth Tønnesen
2026-09-10 22:17 ` [RFC PATCH net-next 6/8] netlink: specs: rt-link: re-align ifla-inet6-stats Asbjørn Sloth Tønnesen
2026-09-10 22:17 ` [RFC PATCH net-next 7/8] netlink: specs: rt-link: fix ifinfo-flags names Asbjørn Sloth Tønnesen
2026-09-10 22:17 ` [RFC PATCH net-next 8/8] netlink: specs: rt-link: fix netkit-policy names Asbjørn Sloth Tønnesen
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=20260910193348.2ded41aa@kernel.org \
--to=kuba@kernel.org \
--cc=ast@fiberby.net \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=gthelen@google.com \
--cc=heng.guo@windriver.com \
--cc=horms@kernel.org \
--cc=i.maximets@ovn.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=one-d-wide@protonmail.com \
--cc=pabeni@redhat.com \
--cc=sdf.kernel@gmail.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