[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y20y8yDgWH42LjMp@unreal>
Date: Thu, 10 Nov 2022 19:20:51 +0200
From: Leon Romanovsky <leon@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Vincent MAILHOL <mailhol.vincent@...adoo.fr>,
netdev@...r.kernel.org, "David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>,
Guangbin Huang <huangguangbin2@...wei.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>
Subject: Re: [PATCH net-next v1] ethtool: ethtool_get_drvinfo: populate
drvinfo fields even if callback exits
On Thu, Nov 10, 2022 at 09:01:27AM -0800, Jakub Kicinski wrote:
> On Thu, 10 Nov 2022 11:11:38 +0200 Leon Romanovsky wrote:
> > I will be happy to see such patch and will review it, but can't add sign-off
> > as I'm not netdev maintainer.
>
> Did we finish the version removal work? :S
Good point :)
>
> Personally I'd rather direct any effort towards writing a checkpatch /
> cocci / python check that catches new cases than cleaning up the pile
> of drivers we have. A lot of which are not actively used..
I thought about this too, but came to conclusion what first step is to
remove "version" from in-kernel API. It will reduce drastically desire
to add driver version to new drivers.
"There is no shame in doing the right thing, even if its too late.".
BTW, I hope that we all learned that allowing drivers to return free
string to users will always lead to disaster.
Thanks
Powered by blists - more mailing lists