From: Johannes Berg <johannes@sipsolutions.net>
To: Alexander Lobakin <alexandr.lobakin@intel.com>,
Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, robh@kernel.org, stephen@networkplumber.org,
ecree.xilinx@gmail.com, sdf@google.com, f.fainelli@gmail.com,
fw@strlen.de, linux-doc@vger.kernel.org, razor@blackwall.org,
nicolas.dichtel@6wind.com
Subject: Re: [PATCH net-next v4 5/8] net: fou: regenerate the uAPI from the spec
Date: Tue, 24 Jan 2023 19:50:40 +0100 [thread overview]
Message-ID: <7d1730862ef79be47f85fc0afd334cda9c3700d5.camel@sipsolutions.net> (raw)
In-Reply-To: <a16382e3-b66f-0a57-2482-72afd00cdabe@intel.com>
On Tue, 2023-01-24 at 18:49 +0100, Alexander Lobakin wrote:
> From: Jakub Kicinski <kuba@kernel.org>
> Date: Fri, 20 Jan 2023 09:50:38 -0800
>
> > Regenerate the FOU uAPI header from the YAML spec.
> >
> > The flags now come before attributes which use them,
> > and the comments for type disappear (coders should look
> > at the spec instead).
>
> Sorry I missed the whole history of this topic. Wanted to ask: if we can
> generate these headers and even C files, why ship the generated with the
> source code and not generate them during building? Or it's slow and/or
> requires some software etc.?
>
Currently it requires python 3 (3.6+, I'd think?).
Python is currently not documented as a build requirement in
Documentation/process/changes.rst afaict.
johannes
next prev parent reply other threads:[~2023-01-24 18:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 17:50 [PATCH net-next v4 0/8] Netlink protocol specs Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 1/8] docs: add more netlink docs (incl. spec docs) Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 2/8] netlink: add schemas for YAML specs Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 3/8] net: add basic C code generators for Netlink Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 4/8] netlink: add a proto specification for FOU Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 5/8] net: fou: regenerate the uAPI from the spec Jakub Kicinski
2023-01-24 17:49 ` Alexander Lobakin
2023-01-24 18:50 ` Johannes Berg [this message]
2023-01-25 0:40 ` Jakub Kicinski
2023-01-25 10:16 ` Alexander Lobakin
2023-01-20 17:50 ` [PATCH net-next v4 6/8] net: fou: rename the source for linking Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 7/8] net: fou: use policy and operation tables generated from the spec Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 8/8] tools: ynl: add a completely generic client Jakub Kicinski
2023-01-24 10:29 ` [PATCH net-next v4 0/8] Netlink protocol specs Paolo Abeni
2023-01-24 10:40 ` 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=7d1730862ef79be47f85fc0afd334cda9c3700d5.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=alexandr.lobakin@intel.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=robh@kernel.org \
--cc=sdf@google.com \
--cc=stephen@networkplumber.org \
/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).