From: Jakub Kicinski <kuba@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Andrew Lunn <andrew@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Donald Hunter <donald.hunter@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Kory Maincent <kory.maincent@bootlin.com>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Nishanth Menon <nm@ti.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, UNGLinuxDriver@microchip.com,
linux-doc@vger.kernel.org, Michal Kubecek <mkubecek@suse.cz>,
Roan van Dijk <roan@protonic.nl>
Subject: Re: [PATCH net-next v2 3/5] ethtool: netlink: add lightweight MSE reporting to LINKSTATE_GET
Date: Mon, 18 Aug 2025 19:35:29 -0700 [thread overview]
Message-ID: <20250818193529.365d49fe@kernel.org> (raw)
In-Reply-To: <20250815063509.743796-4-o.rempel@pengutronix.de>
On Fri, 15 Aug 2025 08:35:07 +0200 Oleksij Rempel wrote:
> diff --git a/include/uapi/linux/ethtool_netlink_generated.h b/include/uapi/linux/ethtool_netlink_generated.h
> index 9c37a96a320b..6ef03a7de4ab 100644
> --- a/include/uapi/linux/ethtool_netlink_generated.h
> +++ b/include/uapi/linux/ethtool_netlink_generated.h
> @@ -322,6 +322,9 @@ enum {
> ETHTOOL_A_LINKSTATE_EXT_STATE,
> ETHTOOL_A_LINKSTATE_EXT_SUBSTATE,
> ETHTOOL_A_LINKSTATE_EXT_DOWN_CNT,
> + ETHTOOL_A_LINKSTATE_MSE_VALUE,
> + ETHTOOL_A_LINKSTATE_MSE_MAX,
> + ETHTOOL_A_LINKSTATE_MSE_CHANNEL,
>
> __ETHTOOL_A_LINKSTATE_CNT,
> ETHTOOL_A_LINKSTATE_MAX = (__ETHTOOL_A_LINKSTATE_CNT - 1)
This changes is not reflected in the YAML spec.
--
pw-bot: cr
next prev parent reply other threads:[~2025-08-19 2:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 6:35 [PATCH net-next v2 0/5] ethtool: introduce PHY MSE diagnostics UAPI and drivers Oleksij Rempel
2025-08-15 6:35 ` [PATCH net-next v2 1/5] ethtool: introduce core UAPI and driver API for PHY MSE diagnostics Oleksij Rempel
2025-08-20 3:03 ` Andrew Lunn
2025-08-20 4:44 ` Oleksij Rempel
2025-08-15 6:35 ` [PATCH net-next v2 2/5] ethtool: netlink: add ETHTOOL_MSG_MSE_GET and wire up PHY MSE access Oleksij Rempel
2025-08-15 6:35 ` [PATCH net-next v2 3/5] ethtool: netlink: add lightweight MSE reporting to LINKSTATE_GET Oleksij Rempel
2025-08-19 2:35 ` Jakub Kicinski [this message]
2025-08-15 6:35 ` [PATCH net-next v2 4/5] net: phy: micrel: add MSE interface support for KSZ9477 family Oleksij Rempel
2025-08-15 6:35 ` [PATCH net-next v2 5/5] net: phy: dp83td510: add MSE interface support for 10BASE-T1L Oleksij Rempel
2025-08-18 8:15 ` Maxime Chevallier
2025-08-18 9:20 ` Oleksij Rempel
2025-08-20 12:11 ` Andrew Lunn
2025-08-20 12:26 ` Oleksij Rempel
2025-08-20 13:32 ` Andrew Lunn
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=20250818193529.365d49fe@kernel.org \
--to=kuba@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kernel@pengutronix.de \
--cc=kory.maincent@bootlin.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=nm@ti.com \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=roan@protonic.nl \
/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).