From: Donald Hunter <donald.hunter@gmail.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Kory Maincent <kory.maincent@bootlin.com>,
Lukasz Majewski <lukma@denx.de>,
Jonathan Corbet <corbet@lwn.net>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Jiri Pirko <jiri@resnulli.us>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Russell King <linux@armlinux.org.uk>,
Divya.Koppera@microchip.com,
Sabrina Dubroca <sd@queasysnail.net>,
Stanislav Fomichev <sdf@fomichev.me>
Subject: Re: [PATCH net-next v4 1/3] tools: ynl-gen: generate kdoc for attribute enums
Date: Tue, 09 Sep 2025 15:05:22 +0100 [thread overview]
Message-ID: <m2qzwfk9gd.fsf@gmail.com> (raw)
In-Reply-To: <20250909072212.3710365-2-o.rempel@pengutronix.de>
Oleksij Rempel <o.rempel@pengutronix.de> writes:
> Parse 'doc' strings from the YAML spec to generate kernel-doc comments
> for the corresponding enums in the C UAPI header, making the headers
> self-documenting.
>
> The generated comment format depends on the documentation available:
> - a full kdoc block ('/**') with @member tags is used if attributes are
> documented
> - a simple block comment ('/*') is used if only the set itself has a doc
> string
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
> tools/net/ynl/pyynl/ynl_gen_c.py | 23 +++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
>
> diff --git a/tools/net/ynl/pyynl/ynl_gen_c.py b/tools/net/ynl/pyynl/ynl_gen_c.py
> index fb7e03805a11..f0a6659797b3 100755
> --- a/tools/net/ynl/pyynl/ynl_gen_c.py
> +++ b/tools/net/ynl/pyynl/ynl_gen_c.py
> @@ -3225,6 +3225,29 @@ def render_uapi(family, cw):
> if attr_set.subset_of:
> continue
>
> + # Write kdoc for attribute-set enums
> + has_main_doc = 'doc' in attr_set.yaml and attr_set.yaml['doc']
> + has_attr_doc = any('doc' in attr for _, attr in attr_set.items())
> +
> + if has_main_doc or has_attr_doc:
> + if has_attr_doc:
> + cw.p('/**')
> + # Construct the main description line for the enum
> + doc_line = f"enum {c_lower(family.ident_name + '_' + attr_set.name)}"
It seems potentially misleading to emit "enum attr-set-name" since they
are anonymous enums.
> + if has_main_doc:
> + doc_line += f" - {attr_set.yaml['doc']}"
> + cw.write_doc_line(doc_line)
> +
> + # Write documentation for each attribute (enum member)
> + for _, attr in attr_set.items():
> + if 'doc' in attr and attr['doc']:
> + doc = f"@{attr.enum_name}: {attr['doc']}"
> + cw.write_doc_line(doc)
> + else: # Only has main doc, use a simpler comment block
> + cw.p('/*')
> + cw.write_doc_line(attr_set.yaml['doc'], indent=False)
> + cw.p(' */')
> +
> max_value = f"({attr_set.cnt_name} - 1)"
>
> val = 0
next prev parent reply other threads:[~2025-09-09 14:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 7:22 [PATCH net-next v4 0/3] Documentation and ynl: add flow control Oleksij Rempel
2025-09-09 7:22 ` [PATCH net-next v4 1/3] tools: ynl-gen: generate kdoc for attribute enums Oleksij Rempel
2025-09-09 14:05 ` Donald Hunter [this message]
2025-09-09 7:22 ` [PATCH net-next v4 2/3] net: ynl: add generated kdoc to UAPI headers Oleksij Rempel
2025-09-09 14:20 ` Donald Hunter
2025-09-09 7:22 ` [PATCH net-next v4 3/3] Documentation: net: add flow control guide and document ethtool API Oleksij Rempel
2025-09-09 14:29 ` Donald Hunter
2025-09-09 21:32 ` [PATCH net-next v4 0/3] Documentation and ynl: add flow control Jakub Kicinski
2025-09-17 10:12 ` Oleksij Rempel
2025-09-17 21:06 ` Jakub Kicinski
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=m2qzwfk9gd.fsf@gmail.com \
--to=donald.hunter@gmail.com \
--cc=Divya.Koppera@microchip.com \
--cc=andrew@lunn.ch \
--cc=ast@kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hawk@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=jiri@resnulli.us \
--cc=john.fastabend@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kory.maincent@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lukma@denx.de \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=sd@queasysnail.net \
--cc=sdf@fomichev.me \
--cc=vadim.fedorenko@linux.dev \
--cc=vladimir.oltean@nxp.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).