[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8597a1d6-d6e2-46a5-87c5-8444a2c7c342@intel.com>
Date: Wed, 18 Jun 2025 12:25:13 +0200
From: Przemek Kitszel <przemyslaw.kitszel@...el.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: "Kaplan, David" <David.Kaplan@....com>, "jedrzej.jagielski@...el.com"
<jedrzej.jagielski@...el.com>, "anthony.l.nguyen@...el.com"
<anthony.l.nguyen@...el.com>, "netdev@...r.kernel.org"
<netdev@...r.kernel.org>, "horms@...nel.org" <horms@...nel.org>, Bharath R
<bharath.r@...el.com>, "regressions@...ts.linux.dev"
<regressions@...ts.linux.dev>, "intel-wired-lan@...ts.osuosl.org"
<intel-wired-lan@...ts.osuosl.org>
Subject: Re: [REGRESSION] ixgbe broken after devlink support patch
On 6/18/25 01:09, Jakub Kicinski wrote:
> On Tue, 17 Jun 2025 11:01:18 +0200 Przemek Kitszel wrote:
>>> Normally, the device is given a name like enp194s0f0 and connects to the wired network.
>>
>> now the name is likely to be different, please see this thread:
>> https://lkml.org/lkml/2025/4/24/1750
>>
>> Is it possible that your network setup script has some part of interface
>> discovery hardcoded?
>
> Hi Przemek, could you/someone on your side try the workaround
> I suggested in the earlier thread? I'm not sure how actively
> developed ixgbe is, if the work is not related to any new devices
> with more complicated port topology breaking people's setups feels
> pretty unnecessary.
yeah, we will fix that, thank you for the remainder
Powered by blists - more mailing lists