From: Jakub Kicinski <kuba@kernel.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "Asbjørn Sloth Tønnesen" <ast@fiberby.net>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Donald Hunter" <donald.hunter@gmail.com>,
"Simon Horman" <horms@kernel.org>,
"Jacob Keller" <jacob.e.keller@intel.com>,
"Sabrina Dubroca" <sd@queasysnail.net>,
wireguard@lists.zx2c4.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v5 00/11] tools: ynl: prepare for wireguard
Date: Tue, 16 Sep 2025 15:39:32 -0700 [thread overview]
Message-ID: <20250916153932.200647ad@kernel.org> (raw)
In-Reply-To: <CAHmME9rf9NGRVtJBnjUJVPraGKL6dk0nRxzXmSi-7X6Y1zjmsA@mail.gmail.com>
On Tue, 16 Sep 2025 17:53:00 +0200 Jason A. Donenfeld wrote:
> On Mon, Sep 15, 2025 at 4:47 PM Asbjørn Sloth Tønnesen <ast@fiberby.net> wrote:
> >
> > This series contains the last batch of YNL changes to support
> > the wireguard YNL conversion.
>
> "the wireguard YNL conversion"
FWIW these patches stand on their own whether we accept the wireguard
patches or not. Put more plainly - please do not read me applying this
set as an endorsement of the larger plan..
> Did I miss some conversation about this? I figure I must have. I must
> say I'm not too keen on wireguard (and apparently only wireguard?)
> being a guinea pig for this.
The specs themselves are gaining maturity. I think adding a YNL spec
for wireguard would be quite nice. Whether we should be converting
the kernel code and uAPI to take advantage of the auto-generation is
a completely separate conversation. If you're not anticipating many
new additions in the uAPI there's little to be gained.
Intro:
https://docs.kernel.org/next/userspace-api/netlink/specs.html
Existing specs:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/tree/Documentation/netlink/specs/
Libs:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/tree/tools/net/ynl/pyynl/lib/ynl.py
https://github.com/linux-netdev/ynl-c (this one is also in tree)
https://github.com/linux-netdev/ynl-cpp
prev parent reply other threads:[~2025-09-16 22:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 14:42 [PATCH net-next v5 00/11] tools: ynl: prepare for wireguard Asbjørn Sloth Tønnesen
2025-09-15 14:42 ` [PATCH net-next v5 01/11] tools: ynl-gen: allow overriding name-prefix for constants Asbjørn Sloth Tønnesen
2025-09-15 14:42 ` [PATCH net-next v5 02/11] tools: ynl-gen: generate nested array policies Asbjørn Sloth Tønnesen
2025-09-15 14:42 ` [PATCH net-next v5 03/11] tools: ynl-gen: add sub-type check Asbjørn Sloth Tønnesen
2025-09-15 14:42 ` [PATCH net-next v5 04/11] tools: ynl-gen: refactor local vars for .attr_put() callers Asbjørn Sloth Tønnesen
2025-09-16 1:42 ` Jakub Kicinski
2025-09-15 14:42 ` [PATCH net-next v5 05/11] tools: ynl-gen: avoid repetitive variables definitions Asbjørn Sloth Tønnesen
2025-09-16 1:42 ` Jakub Kicinski
2025-09-15 14:42 ` [PATCH net-next v5 06/11] tools: ynl-gen: validate nested arrays Asbjørn Sloth Tønnesen
2025-09-16 1:42 ` Jakub Kicinski
2025-09-15 14:42 ` [PATCH net-next v5 07/11] tools: ynl-gen: rename TypeArrayNest to TypeIndexedArray Asbjørn Sloth Tønnesen
2025-09-16 1:43 ` Jakub Kicinski
2025-09-15 14:42 ` [PATCH net-next v5 08/11] tools: ynl: move nest packing to a helper function Asbjørn Sloth Tønnesen
2025-09-15 14:42 ` [PATCH net-next v5 09/11] tools: ynl: encode indexed-arrays Asbjørn Sloth Tønnesen
2025-09-15 14:42 ` [PATCH net-next v5 10/11] tools: ynl: decode hex input Asbjørn Sloth Tønnesen
2025-09-15 14:42 ` [PATCH net-next v5 11/11] tools: ynl: add ipv4-or-v6 display hint Asbjørn Sloth Tønnesen
2025-09-16 15:38 ` [PATCH net-next v5 00/11] tools: ynl: prepare for wireguard patchwork-bot+netdevbpf
2025-09-16 15:53 ` Jason A. Donenfeld
2025-09-16 22:39 ` Jakub Kicinski [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=20250916153932.200647ad@kernel.org \
--to=kuba@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ast@fiberby.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=wireguard@lists.zx2c4.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).