Setting the link down does not necessarily change the carrier state for
virtual interfaces like bonding. Therefore, handling the device up/down
event via netif_stacked_transfer_operstate() is not sufficient.
If the lower link and macvlan are in different namespaces, the upper link
state may become
On 3/4/25 14:26, Mark Brown wrote:
On Thu, Apr 03, 2025 at 02:19:40PM +0800, David Gow wrote:
That being said, there are a _lot_ of Cirrus FW tests (over 5000 by my
count when all of the parameterised ones are taken into account), so
this can still trigger the default 5-minute kunit.py timeout.
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski :
On Thu, 3 Apr 2025 07:56:36 -0700 you wrote:
> Our CI expects output from the test at least once every 10 minutes.
> The AMT test when running on debug kernel is just on the edge
> of that time for the stress test. Improv
On Fri, Apr 04, 2025 at 12:10:13PM +0100, Richard Fitzgerald wrote:
> On 4/4/25 07:53, David Gow wrote:
> > - Make sure these tests don't automatically enable themselves if no
> > driver which depends on the firmware loader is enabled. (e.g. make it
> > depend on the library, rather than selecting
When hds-thresh is configured, ethnl_set_rings() is called, and it calls
ethtool_ringparam_get_cfg() to get ringparameters from .get_ringparam()
callback and dev->cfg.
Both hds_config and hds_thresh values should be set from dev->cfg, not
from .get_ringparam().
But ethtool_ringparam_get_cfg() sets
A hds-thresh value is not set correctly if input value is 0.
The cause is that ethtool_ringparam_get_cfg(), which is a internal
function that returns ringparameters from both ->get_ringparam() and
dev->cfg can't return a correct hds-thresh value.
The first patch fixes ethtool_ringparam_get_cfg() t
hds.py has been testing 0(set_hds_thresh_zero()),
MAX(set_hds_thresh_max()), GT(set_hds_thresh_gt()) values for hds-thresh.
However if a hds-thresh value was already 0, set_hds_thresh_zero()
can't test properly.
So, it tests random value first and then tests 0, MAX, GT values.
Testing bnxt:
TA
On 4/4/25 07:53, David Gow wrote:
On Fri, 4 Apr 2025 at 01:48, Mark Brown wrote:
On Thu, Apr 03, 2025 at 05:57:51PM +0100, Richard Fitzgerald wrote:
On 3/4/25 14:26, Mark Brown wrote:
I've not heard anyone mention hitting the timeouts, though now I run
interactively I do see that the Cirru
Hi Thomas
Following posix_timers kself test failed in 6.12.y
-
not ok 7 check_sig_ign SIGEV_SIGNAL
not ok 9 check_rearm
not ok 10 check_delete
-
Reason of failure:
6.12.y does not support these KSELT tests,
Because the following commits were not ba
On Fri, 4 Apr 2025 at 01:48, Mark Brown wrote:
>
> On Thu, Apr 03, 2025 at 05:57:51PM +0100, Richard Fitzgerald wrote:
> > On 3/4/25 14:26, Mark Brown wrote:
>
> > > I've not heard anyone mention hitting the timeouts, though now I run
> > > interactively I do see that the Cirrus stuff is a good pr
10 matches
Mail list logo
