[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y2vozcC2ahbhAvhM@unreal>
Date: Wed, 9 Nov 2022 19:52:13 +0200
From: Leon Romanovsky <leon@...nel.org>
To: Vincent Mailhol <mailhol.vincent@...adoo.fr>
Cc: netdev@...r.kernel.org, "David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Guangbin Huang <huangguangbin2@...wei.com>,
Hao Chen <chenhao288@...ilicon.com>,
Sean Anderson <sean.anderson@...o.com>,
Tom Rix <trix@...hat.com>,
Tonghao Zhang <xiangxia.m.yue@...il.com>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
Marco Bonelli <marco@...eim.net>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v1] ethtool: ethtool_get_drvinfo: populate
drvinfo fields even if callback exits
On Tue, Nov 08, 2022 at 12:57:54PM +0900, Vincent Mailhol wrote:
> If ethtool_ops::get_drvinfo() callback isn't set,
> ethtool_get_drvinfo() will fill the ethtool_drvinfo::name and
> ethtool_drvinfo::bus_info fields.
>
> However, if the driver provides the callback function, those two
> fields are not touched. This means that the driver has to fill these
> itself.
Can you please point to such drivers? One can argue that they don't need
to touch these fields in a first place and ethtool_drvinfo should always
overwrite them.
Thanks
Powered by blists - more mailing lists