From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, "Andrew Lunn" <andrew@lunn.ch>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Russell King" <linux@armlinux.org.uk>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com,
"Christophe Leroy" <christophe.leroy@csgroup.eu>,
"Herve Codina" <herve.codina@bootlin.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Vladimir Oltean" <vladimir.oltean@nxp.com>,
"Köry Maincent" <kory.maincent@bootlin.com>,
"Marek Behún" <kabel@kernel.org>,
"Oleksij Rempel" <o.rempel@pengutronix.de>,
"Nicolò Veronese" <nicveronese@gmail.com>,
"Simon Horman" <horms@kernel.org>,
mwojtas@chromium.org,
"Romain Gantois" <romain.gantois@bootlin.com>,
"Daniel Golle" <daniel@makrotopia.org>,
"Dimitri Fedrau" <dimitri.fedrau@liebherr.com>,
"Frank Wunderlich" <frank.wunderlich@linux.dev>,
"Pietro Ameruoso" <p.ameruoso@live.it>
Subject: Re: [PATCH net-next v15 00/10] net: phy_port: SFP modules representation and phy_port listing
Date: Tue, 4 Aug 2026 09:21:33 +0200 [thread overview]
Message-ID: <5c1b3bdd-37a9-45d0-90d2-1afc78125972@bootlin.com> (raw)
In-Reply-To: <20260803140431.2bbe2949@kernel.org>
Hi,
On 8/3/26 23:04, Jakub Kicinski wrote:
> On Sat, 1 Aug 2026 09:43:21 +0200 Maxime Chevallier wrote:
>> Here's V15 for the phy_port improved SFP support and netlink interface.
>
> Breaks YNL build:
>
> In file included from ethtool-user.c:10:
> ethtool-user.h:8523:42: error: field 'obj' has incomplete type
> 8523 | struct ethtool_port_get_rsp_dump obj __attribute__((aligned(8)));
> | ^~~
> ethtool-user.c: In function 'ethtool_port_get_dump':
> ethtool-user.c:8833:18: error: 'ethtool_port_get_rsp_dump_parse' undeclared
> (first use in this function); did you mean 'ethtool_port_get_rsp_parse'?
> ethtool-user.c:8847:19: error: returning 'void *' from a function with return
> type 'int' makes integer from pointer without a cast
> ethtool-user.c:8851:16: error: returning 'void *' from a function with return
> type 'int' makes integer from pointer without a cast
> make[1]: *** [Makefile:52: ethtool-user.o] Error 1
> make: *** [Makefile:57: ../generated/protos.a] Error 2
>
> You need to specify the reply for dump, I didn't check if it matches do
> but if it does:
Ah correct, that's my bad I disabled ynl build temporarily as it doesn't
play well with cross-compile, let me fix this issue and see what I can
do with the ynl build in itself
Maxime
>
> --- a/Documentation/netlink/specs/ethtool.yaml
> +++ b/Documentation/netlink/specs/ethtool.yaml
> @@ -2896,12 +2896,12 @@ c-version-name: ethtool-genl-version
>
> attribute-set: port
>
> - do: &port-get-op
> + do:
> request:
> attributes:
> - header
> - id
> - reply:
> + reply: &port-get-op-reply
> attributes:
> - header
> - id
> @@ -2913,6 +2913,7 @@ c-version-name: ethtool-genl-version
> request:
> attributes:
> - header
> + reply: *port-get-op-reply
>
> mcast-groups:
> list:
prev parent reply other threads:[~2026-08-04 7:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 7:43 [PATCH net-next v15 00/10] net: phy_port: SFP modules representation and phy_port listing Maxime Chevallier
2026-08-01 7:43 ` [PATCH net-next v15 01/10] net: phy: phy_link_topology: Add a helper for opportunistic alloc Maxime Chevallier
2026-08-01 7:43 ` [PATCH net-next v15 02/10] net: phy: phy_link_topology: Track ports in phy_link_topology Maxime Chevallier
2026-08-01 7:43 ` [PATCH net-next v15 03/10] net: phylink: Register a phy_port for MAC-driven SFP cages Maxime Chevallier
2026-08-01 7:43 ` [PATCH net-next v15 04/10] net: phy: Create SFP phy_port before registering upstream Maxime Chevallier
2026-08-01 7:43 ` [PATCH net-next v15 05/10] net: phy: Represent PHY-less SFP modules with phy_port Maxime Chevallier
2026-08-01 7:43 ` [PATCH net-next v15 06/10] net: phy: phy_port: Store information about a port's upstream Maxime Chevallier
2026-08-01 7:43 ` [PATCH net-next v15 07/10] net: phy: phy_link_topology: Add a helper to retrieve ports Maxime Chevallier
2026-08-01 7:43 ` [PATCH net-next v15 08/10] netlink: specs: Add ethernet port listing with ethtool Maxime Chevallier
2026-08-01 7:43 ` [PATCH net-next v15 09/10] net: ethtool: Introduce ethtool command to list ports Maxime Chevallier
2026-08-01 7:43 ` [PATCH net-next v15 10/10] Documentation: networking: Update the phy_port infrastructure description Maxime Chevallier
2026-08-03 21:04 ` [PATCH net-next v15 00/10] net: phy_port: SFP modules representation and phy_port listing Jakub Kicinski
2026-08-04 7:21 ` Maxime Chevallier [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=5c1b3bdd-37a9-45d0-90d2-1afc78125972@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=andrew@lunn.ch \
--cc=christophe.leroy@csgroup.eu \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=dimitri.fedrau@liebherr.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=frank.wunderlich@linux.dev \
--cc=herve.codina@bootlin.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kabel@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mwojtas@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=nicveronese@gmail.com \
--cc=o.rempel@pengutronix.de \
--cc=p.ameruoso@live.it \
--cc=pabeni@redhat.com \
--cc=romain.gantois@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--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