[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240222084948.16f33760@device-28.home>
Date: Thu, 22 Feb 2024 08:49:48 +0100
From: Maxime Chevallier <maxime.chevallier@...tlin.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, thomas.petazzoni@...tlin.com, Andrew Lunn
<andrew@...n.ch>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
<pabeni@...hat.com>, Russell King <linux@...linux.org.uk>,
linux-arm-kernel@...ts.infradead.org, Christophe Leroy
<christophe.leroy@...roup.eu>, Herve Codina <herve.codina@...tlin.com>,
Florian Fainelli <f.fainelli@...il.com>, Heiner Kallweit
<hkallweit1@...il.com>, Vladimir Oltean <vladimir.oltean@....com>,
Köry Maincent <kory.maincent@...tlin.com>, Jesse Brandeburg
<jesse.brandeburg@...el.com>, Jonathan Corbet <corbet@....net>, Marek
Behún <kabel@...nel.org>, Piergiorgio Beruto
<piergiorgio.beruto@...il.com>, Oleksij Rempel <o.rempel@...gutronix.de>,
Nicolò Veronese <nicveronese@...il.com>, Simon Horman
<horms@...nel.org>, mwojtas@...omium.org
Subject: Re: [PATCH net-next v8 08/13] netlink: specs: add ethnl PHY_GET
command set
Hello Jakub,
On Wed, 21 Feb 2024 17:00:23 -0800
Jakub Kicinski <kuba@...nel.org> wrote:
> On Tue, 20 Feb 2024 19:42:11 +0100 Maxime Chevallier wrote:
> > + -
> > + name: upstream-phy-index
> > + type: u32
>
> The C define appears to be called:
>
> ETHTOOL_A_PHY_UPSTREAM_INDEX, /* u32 */
>
> either it needs to gain the PHY_ or the spec needs to lose the phy-,
> otherwise C code gen gets upset:
I'll do it, sorry about that.
>
> ethtool-user.c:689:10: error: ‘ETHTOOL_A_PHY_UPSTREAM_PHY_INDEX’ undeclared here (not in a function); did you mean ‘ETHTOOL_A_PHY_UPSTREAM_INDEX’?
> 689 | [ETHTOOL_A_PHY_UPSTREAM_PHY_INDEX] = { .name = "upstream-phy-index", .type = YNL_PT_U32, },
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> | ETHTOOL_A_PHY_UPSTREAM_INDEX
>
> Unfortunately ethtool in the in-between state where we can auto-gen
> user space code (or rather most of it) but the uAPI header is not
> auto-generated so we need to take extra care to keep things in sync :(
Is there anything I run for testing, so that I can make sure this
doesn't happen again ?
Thanks,
Maxime
Powered by blists - more mailing lists