netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Donald Hunter <donald.hunter@gmail.com>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	 Eric Dumazet <edumazet@google.com>,
	 Jakub Kicinski <kuba@kernel.org>,
	 Paolo Abeni <pabeni@redhat.com>,
	 Oleksij Rempel <o.rempel@pengutronix.de>,
	 Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	 linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	 Dent Project <dentproject@linuxfoundation.org>,
	kernel@pengutronix.de
Subject: Re: [PATCH net-next v3 2/7] netlink: specs: Expand the PSE netlink command with C33 new features
Date: Mon, 17 Jun 2024 09:01:28 +0100	[thread overview]
Message-ID: <m2frtc9ew7.fsf@gmail.com> (raw)
In-Reply-To: <20240614-feature_poe_power_cap-v3-2-a26784e78311@bootlin.com> (Kory Maincent's message of "Fri, 14 Jun 2024 16:33:18 +0200")

Kory Maincent <kory.maincent@bootlin.com> writes:

> diff --git a/Documentation/netlink/specs/ethtool.yaml b/Documentation/netlink/specs/ethtool.yaml
> index 00dc61358be8..0ff27319856c 100644
> --- a/Documentation/netlink/specs/ethtool.yaml
> +++ b/Documentation/netlink/specs/ethtool.yaml
> @@ -20,6 +20,20 @@ definitions:
>      name: header-flags
>      type: flags
>      entries: [ compact-bitsets, omit-reply, stats ]
> +  -
> +    name: c33-pse-ext-state
> +    enum-name:
> +    type: enum
> +    entries: [ none,
> +               ethtool_c33_pse_ext_state_class_num_events,
> +               ethtool_c33_pse_ext_state_error_condition,
> +               ethtool_c33_pse_ext_state_mr_pse_enable,
> +               ethtool_c33_pse_ext_state_option_detect_ted,
> +               ethtool_c33_pse_ext_state_option_vport_lim,
> +               ethtool_c33_pse_ext_state_ovld_detected,
> +               ethtool_c33_pse_ext_state_pd_dll_power_type,
> +               ethtool_c33_pse_ext_state_power_not_available,
> +               ethtool_c33_pse_ext_state_short_detected ]

It looks like this should use name-prefix: ethtool-c33-pse-ext-state- so
that all the entries can be shortened.

The entries should be in hyphen-case, not snake_case.

The preferred format for a list that spills over many lines is to use
the yaml list format:

    entries:
      - none
      - class-num-events
      - error-condition
      - mr-pse-enable
      ...

Thanks!
--
Donald Hunter.

  reply	other threads:[~2024-06-17  8:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14 14:33 [PATCH net-next v3 0/7] net: pse-pd: Add new PSE c33 features Kory Maincent
2024-06-14 14:33 ` [PATCH net-next v3 1/7] net: ethtool: pse-pd: Expand C33 PSE status with class, power and extended state Kory Maincent
2024-06-15 11:22   ` Oleksij Rempel
2024-06-17 13:47     ` Kory Maincent
2024-06-17 19:55       ` Oleksij Rempel
2024-06-21 16:29         ` Kory Maincent
2024-06-22  5:06           ` Oleksij Rempel
2024-06-25  9:18         ` Kory Maincent
2024-06-25 10:33           ` Oleksij Rempel
2024-06-25 11:59             ` Kory Maincent
2024-06-14 14:33 ` [PATCH net-next v3 2/7] netlink: specs: Expand the PSE netlink command with C33 new features Kory Maincent
2024-06-17  8:01   ` Donald Hunter [this message]
2024-06-14 14:33 ` [PATCH net-next v3 3/7] net: pse-pd: pd692x0: Expand ethtool status message Kory Maincent
2024-06-14 14:33 ` [PATCH net-next v3 4/7] net: pse-pd: Add new power limit get and set c33 features Kory Maincent
2024-06-14 14:33 ` [PATCH net-next v3 5/7] net: ethtool: Add new power limit get and set features Kory Maincent
2024-06-15 15:59   ` Oleksij Rempel
2024-06-15 18:28     ` Oleksij Rempel
2024-06-16  6:07       ` Oleksij Rempel
2024-06-17 16:14         ` Kory Maincent
2024-06-17 19:57           ` Oleksij Rempel
2024-06-14 14:33 ` [PATCH net-next v3 6/7] netlink: specs: Expand the PSE netlink command with C33 pw-limit attributes Kory Maincent
2024-06-17  8:03   ` Donald Hunter
2024-06-17  9:53     ` Kory Maincent
2024-06-14 14:33 ` [PATCH net-next v3 7/7] net: pse-pd: pd692x0: Enhance with new current limit and voltage read callbacks Kory Maincent

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=m2frtc9ew7.fsf@gmail.com \
    --to=donald.hunter@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dentproject@linuxfoundation.org \
    --cc=edumazet@google.com \
    --cc=kernel@pengutronix.de \
    --cc=kory.maincent@bootlin.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=pabeni@redhat.com \
    --cc=thomas.petazzoni@bootlin.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).