[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <B649FE55-96A3-4631-8714-51128EDEE810@net-swift.com>
Date: Thu, 26 Jun 2025 14:31:36 +0800
From: "mengyuanlou@...-swift.com" <mengyuanlou@...-swift.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org,
michal.swiatkowski@...ux.intel.com,
kuba@...nel.org,
pabeni@...hat.com,
horms@...nel.org,
andrew+netdev@...n.ch,
duanqiangwen@...-swift.com,
linglingzhang@...stnetic.com,
jiawenwu@...-swift.com
Subject: Re: [PATCH net-next v2 08/12] net: txgbevf: add phylink check flow
> 2025年6月26日 01:08,Andrew Lunn <andrew@...n.ch> 写道:
>
> On Wed, Jun 25, 2025 at 06:20:54PM +0800, Mengyuan Lou wrote:
>> Add phylink support to wangxun 10/25/40G virtual functions.
>
> What do you gain by having a phylink instance for a VF?
>
> All the ops you define are basically NOPs. What is phylink actually
> doing?
I think phylink helps me monitor the changes in link status and
automatically set the netif status.
Besides, I can also directly use the get_link_ksettings interface.
>
> Andrew
>
Powered by blists - more mailing lists