diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2025-11-20 20:02:55 -0800 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2025-11-24 18:51:40 -0800 |
| commit | f81171fecd0c33f442fe3aa94cff650d0069152a (patch) | |
| tree | 21ae37d340a247b067ab9ae293bbcfabbf7cd818 /net/unix/unix_bpf.c | |
| parent | ef0b78b5b6cb139af1273fc5f2720201556b2650 (diff) | |
selftests: hw-net: auto-disable building the iouring C code
Looks like the liburing is not updated by distros very aggressively.
Presumably because a lot of packages depend on it. I just updated
to Fedora 43 and it's still on liburing 2.9. The test is 9mo old,
at this stage I think this warrants handling the build failure
more gracefully.
Detect if iouring is recent enough and if not print a warning
and exclude the C prog from build. The Python test will just
fail since the binary won't exist. But it removes the major
annoyance of having to update liburing from sources when
developing other tests.
Reviewed-by: Willem de Bruijn <willemb@google.com>
Link: https://patch.msgid.link/20251121040259.3647749-2-kuba@kernel.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'net/unix/unix_bpf.c')
0 files changed, 0 insertions, 0 deletions
