diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2026-10-20 20:22:24 -0700 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-10-20 20:22:24 -0700 |
| commit | 78974bac98eb0581f85aab56ccc0377cdcedb964 (patch) | |
| tree | 2477ea25b42cc509ffb8aec8218147d11bf0e4a5 /scripts/Makefile.thinlto | |
| parent | 4a929eba247b7cde87fa2a9cf6033301fdd2981a (diff) | |
| parent | aca2542b886dc64c4f7c7fe67647ca971d3f0794 (diff) | |
| download | linux-78974bac98eb0581f85aab56ccc0377cdcedb964.tar.gz linux-78974bac98eb0581f85aab56ccc0377cdcedb964.zip | |
Merge branch 'selftests-drv-net-introduce-flow-control-selftest'
Maxime Chevallier says:
====================
selftests: drv-net: Introduce flow-control selftest
This test aims at validating the flow control implementation in drivers,
using the ethtool API.
The test can run in various conditions :
DUT <-----> Anything that has link up (not controllable)
DUT <-----> A directly connected device
It enumerates the local and remote device's capabilities, to test as
much as possibly testable. I've run it on 17 different boards connected
to other boards through various means : Usb to Eth dongles, direct
connection to the board, connection through a switch. Some of the ports
tested were user ports of DSA switches too.
Contrary to V2, on V3 we really only have a collection of actual
failures that show during tests, as one of the peer's I'm running these
on has a v6.18 kernel that pre-dates the realtek phylink port and show
actual bugs in the driver.
====================
Link: https://patch.msgid.link/20261015134350.629593-1-maxime.chevallier@bootlin.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions
