From: Jakub Kicinski <kuba@kernel.org>
To: Stanislav Fomichev <stfomichev@gmail.com>
Cc: Stanislav Fomichev <sdf@fomichev.me>,
netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, horms@kernel.org,
donald.hunter@gmail.com, corbet@lwn.net, andrew+netdev@lunn.ch,
kory.maincent@bootlin.com, nicolas.dichtel@6wind.com
Subject: Re: [PATCH net-next v3 0/8] ethtool: generate uapi header from the spec
Date: Tue, 3 Dec 2024 18:39:05 -0800 [thread overview]
Message-ID: <20241203183905.3343d9a5@kernel.org> (raw)
In-Reply-To: <Z06SGszVaXopVlhR@mini-arch>
On Mon, 2 Dec 2024 21:07:38 -0800 Stanislav Fomichev wrote:
> diff --git a/Documentation/netlink/specs/ethtool.yaml b/Documentation/netlink/specs/ethtool.yaml
> index efa00665c191..859ae0cb1fd8 100644
> --- a/Documentation/netlink/specs/ethtool.yaml
> +++ b/Documentation/netlink/specs/ethtool.yaml
> @@ -60,7 +60,8 @@ uapi-header: linux/ethtool_netlink_generated.h
> name-prefix: ethtool-c33-pse-ext-state-
> header: linux/ethtool.h
> entries:
> - - none
> + - name: none
> + doc: none
>
> The first one fixes the bullet list (seems like mixing entries with and
> without docs confuses ynl-gen-rst.py).
Ah, yes, that makes sense, either all entries should be objects or all
should be strings. I will spare you trying to figure out how to enforce
that in jsonschema :)
nit: "-" and "name: none" on separate lines
> -
> name: error-condition
> doc: Group of error_condition states
> @@ -875,15 +876,15 @@ uapi-header: linux/ethtool_netlink_generated.h
> value: 0
> -
> name: pair
> - doc: ETHTOOL_A_CABLE_PAIR_
> + doc: ETHTOOL_A_CABLE_PAIR
> type: u8
> -
> name: code
> - doc: ETHTOOL_A_CABLE_RESULT_CODE_
> + doc: ETHTOOL_A_CABLE_RESULT_CODE
> type: u8
> -
> name: src
> - doc: ETHTOOL_A_CABLE_INF_SRC_
> + doc: ETHTOOL_A_CABLE_INF_SRC
> type: u32
> -
> name: cable-fault-length
>
> And removing trailing _ fixes the rest (don't know why).
Mmm. Trailing _ must mean something in ReST.
Can't decide now whether we care more about supporting ReST formatting
in YAML docs or protecting unsuspecting developers from this sort of a
surprise. So let's do the easier thing for now.
> Any objections to folding it as is into v4? I can go on and try to
> understand why ynl-gen-rst.py behaves exactly that way, but not sure
> it would buy us anything?
Yup, v4 with more or less the diff above SGTM!
prev parent reply other threads:[~2024-12-04 2:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 16:29 [PATCH net-next v3 0/8] ethtool: generate uapi header from the spec Stanislav Fomichev
2024-12-02 16:29 ` [PATCH net-next v3 1/8] ynl: support enum-cnt-name attribute in legacy definitions Stanislav Fomichev
2024-12-02 16:29 ` [PATCH net-next v3 2/8] ynl: skip rendering attributes with header property in uapi mode Stanislav Fomichev
2024-12-02 16:29 ` [PATCH net-next v3 3/8] ynl: support directional specs in ynl-gen-c.py Stanislav Fomichev
2024-12-02 16:29 ` [PATCH net-next v3 4/8] ynl: add missing pieces to ethtool spec to better match uapi header Stanislav Fomichev
2024-12-02 16:29 ` [PATCH net-next v3 5/8] ynl: include uapi header after all dependencies Stanislav Fomichev
2024-12-02 16:29 ` [PATCH net-next v3 6/8] ethtool: separate definitions that are gonna be generated Stanislav Fomichev
2024-12-02 16:29 ` [PATCH net-next v3 7/8] ethtool: remove the comments that are not " Stanislav Fomichev
2024-12-02 16:29 ` [PATCH net-next v3 8/8] ethtool: regenerate uapi header from the spec Stanislav Fomichev
2024-12-03 3:52 ` [PATCH net-next v3 0/8] ethtool: generate " Jakub Kicinski
2024-12-03 5:07 ` Stanislav Fomichev
2024-12-04 2: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=20241203183905.3343d9a5@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=stfomichev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.