Re: [Patch v3 net-next 6/7] octeontx2-pf: ethtool physical link status

2021-02-04 Thread Hariprasad Kelam
ovvuri Goutham ; Linu > Cherian ; Geethasowjanya Akula > ; Jerin Jacob Kollanukkaran ; > Subbaraya Sundeep Bhatta > Subject: [EXT] Re: [Patch v3 net-next 6/7] octeontx2-pf: ethtool physical link > status > > External Email > > ---

Re: [Patch v3 net-next 6/7] octeontx2-pf: ethtool physical link status

2021-02-02 Thread Jakub Kicinski
On Sun, 31 Jan 2021 18:41:04 +0530 Hariprasad Kelam wrote: > From: Christina Jacob > > Register get_link_ksettings callback to get link status information > from the driver. As virtual function (vf) shares same physical link > same API is used for both the drivers and for loop back drivers >

Re: [Patch v3 net-next 6/7] octeontx2-pf: ethtool physical link status

2021-02-02 Thread Jesse Brandeburg
Hariprasad Kelam wrote: > From: Christina Jacob > > Register get_link_ksettings callback to get link status information > from the driver. As virtual function (vf) shares same physical link > same API is used for both the drivers and for loop back drivers > simply returns the fixed values as

[Patch v3 net-next 6/7] octeontx2-pf: ethtool physical link status

2021-01-31 Thread Hariprasad Kelam
From: Christina Jacob Register get_link_ksettings callback to get link status information from the driver. As virtual function (vf) shares same physical link same API is used for both the drivers and for loop back drivers simply returns the fixed values as its does not have physical link.

[Patch v3 net-next 6/7] octeontx2-pf: ethtool physical link status

2021-01-31 Thread Hariprasad Kelam
From: Christina Jacob Register get_link_ksettings callback to get link status information from the driver. As virtual function (vf) shares same physical link same API is used for both the drivers and for loop back drivers simply returns the fixed values as its does not have physical link.