[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d9131fb7-a6fe-43a4-92c6-5577700e34bf@stanley.mountain>
Date: Tue, 27 Aug 2024 12:17:43 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Maxime Chevallier <maxime.chevallier@...tlin.com>
Cc: Pengfei Xu <pengfei.xu@...el.com>, davem@...emloft.net,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
thomas.petazzoni@...tlin.com, Andrew Lunn <andrew@...n.ch>,
Jakub Kicinski <kuba@...nel.org>,
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>,
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,
Nathan Chancellor <nathan@...nel.org>,
Antoine Tenart <atenart@...nel.org>,
Marc Kleine-Budde <mkl@...gutronix.de>,
Romain Gantois <romain.gantois@...tlin.com>
Subject: Re: [PATCH net-next v17 11/14] net: ethtool: cable-test: Target the
command to the requested PHY
On Tue, Aug 27, 2024 at 10:48:25AM +0200, Maxime Chevallier wrote:
> Hi again Dan,
>
> On Tue, 27 Aug 2024 11:27:48 +0300
> Dan Carpenter <dan.carpenter@...aro.org> wrote:
>
>
> > Could you add some comments to ethnl_req_get_phydev() what the NULL return
> > means vs the error pointers? I figured it out because the callers have comments
> > but it should be next to ethnl_req_get_phydev() as well.
>
> Actually I replied a bit too fast, this is already documented :
> https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/tree/net/ethtool/netlink.h#n284
>
> Is this doc clear enough or should I still add some more explicit
> comments ?
>
Ah, I didn't see that. Thanks.
That comment is fine but we normally would have put it next to the function
implementation instead of the header file. There are lots of comments in the
header file, sure, but those are for inline functions so it's the same rule of
thumb that the comments are next to the implementation.
regards,
dan carpenter
Powered by blists - more mailing lists