[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d81820e1-21e0-4c59-8532-ba55ac47c6fd@nvidia.com>
Date: Wed, 26 Nov 2025 10:06:18 +0200
From: Carolina Jubran <cjubran@...dia.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Shuah Khan <shuah@...nel.org>, Andrew Lunn <andrew+netdev@...n.ch>,
"David S . Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
Gal Pressman <gal@...dia.com>, Tariq Toukan <tariqt@...dia.com>,
Cosmin Ratiu <cratiu@...dia.com>, Nimrod Oren <noren@...dia.com>,
Mark Bloch <mbloch@...dia.com>, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH net-next V2 0/6] selftests: drv-net: Fix issues in
devlink_rate_tc_bw.py
On 25/11/2025 5:10, Jakub Kicinski wrote:
> On Sun, 23 Nov 2025 19:10:09 +0200 Carolina Jubran wrote:
>> This series fixes issues in the devlink_rate_tc_bw.py selftest and
>> introduces a new Iperf3Runner that helps with measurement handling.
> Sorry to report but patch 2 doesn't apply cleanly.
I am based on top of net-next, and I do not see any issues applying the
series. I rebased on top of commit ab084f0b8d6d2ee4b1c6a28f39a2a7430bdfa7f0
and patch 2 still applies cleanly for me.
I’ll prepare a v3 to fix the new pylint warnings in load.py while I’m at
it.
If you are applying it on a different base, please let me know which
one.
Thanks,
Carolina
Powered by blists - more mailing lists