[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240402074551.12c4fa03@kernel.org>
Date: Tue, 2 Apr 2024 07:45:51 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jiri Pirko <jiri@...nulli.us>
Cc: Hangbin Liu <liuhangbin@...il.com>, netdev@...r.kernel.org, "David S.
Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo
Abeni <pabeni@...hat.com>, Donald Hunter <donald.hunter@...il.com>, Jacob
Keller <jacob.e.keller@...el.com>, Stanislav Fomichev <sdf@...gle.com>
Subject: Re: [PATCHv4 net-next 1/4] Documentation: netlink: add a YAML spec
for team
On Tue, 2 Apr 2024 14:22:53 +0200 Jiri Pirko wrote:
> For the record, this is incomplete as this is not of type "binary" but
> rather a type determined by TEAM_ATTR_OPTION_TYPE.
> My rejected patch:
> https://lore.kernel.org/all/20240219172525.71406-7-jiri@resnulli.us/
> Makes that possible to be implemented in ynl.
>
> Jakub, still not willing to pull this in?
Yes, I think I said this in the first LPC talk about YNL.
My main goal is to make support for higher level languages seamless.
That means someone needs to write a code gen or ynl.py-like
integration for Go, Rust or C++ (proper C++ one not just a copy
of the C code gen). Complicating the specs makes that less likely.
Powered by blists - more mailing lists