[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y2I5X4eMnisedAE5@nanopsycho>
Date: Wed, 2 Nov 2022 10:33:19 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Jakub Kicinski <kuba@...nel.org>
Cc: netdev@...r.kernel.org, davem@...emloft.net, pabeni@...hat.com,
edumazet@...gle.com, tariqt@...dia.com, moshe@...dia.com,
saeedm@...dia.com, linux-rdma@...r.kernel.org
Subject: Re: [patch net-next v3 00/13] net: fix netdev to devlink_port
linkage and expose to user
Tue, Nov 01, 2022 at 06:29:15PM CET, kuba@...nel.org wrote:
>On Mon, 31 Oct 2022 13:42:35 +0100 Jiri Pirko wrote:
>> Currently, the info about linkage from netdev to the related
>> devlink_port instance is done using ndo_get_devlink_port().
>> This is not sufficient, as it is up to the driver to implement it and
>> some of them don't do that. Also it leads to a lot of unnecessary
>> boilerplate code in all the drivers.
>
>Sorry about the late nit picks, the other patches look good.
Nevermind, will fix those.
>Nice cleanup!
Thx!
Powered by blists - more mailing lists