[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <457036b2-cc6c-45db-98fb-3967c535402e@redhat.com>
Date: Thu, 21 Aug 2025 17:02:00 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: Jakub Kicinski <kuba@...nel.org>, Taehee Yoo <ap420073@...il.com>
Cc: netdev@...r.kernel.org, edumazet@...gle.com, andrew+netdev@...n.ch,
horms@...nel.org, almasrymina@...gle.com, michael.chan@...adcom.com,
tariqt@...dia.com, dtatulea@...dia.com, hawk@...nel.org,
ilias.apalodimas@...aro.org, alexanderduyck@...com, sdf@...ichev.me,
davem@...emloft.net
Subject: Re: [PATCH net-next 00/15] eth: fbnic: support queue API and
zero-copy Rx
On 8/21/25 4:28 PM, Jakub Kicinski wrote:
> On Thu, 21 Aug 2025 09:51:55 +0200 Paolo Abeni wrote:
>> Blindly noting
>
> I haven't looked closely either :) but my gut feeling is that this
> is because the devmem test doesn't clean up after itself. It used to
> bail out sooner, with this series is goes further in messing up the
> config, and then all tests that run after have a misconfigured NIC..
Possibly I was not clear in my previous email: I suspect that the
ping.py issue is a real one/tied to driver changes - even if already
merged ones and not to the pending patches.
/P
Powered by blists - more mailing lists