Hi everyone,

Here a small series to address some of the issues found while trying to run
the drivers/net/hw selftests on some variety of embedded devices. In
that case, tests are cross-compiled and installed to the rootfs with the
'install' target of the selftests.

Some tests require ynl, and ynl's build machinery hardcodes CC to gcc,
which doesn't work with cross-compiled setups. Let's use the
tools/scripts/Makefile.include instead.

This is duplicated across the ynl tools as it seems to be fairly common
to build alone.

Let's also deal with the io_uring zerocopy check that builds a tiny program
to verify that liburing is available and in the right version.

Maxime Chevallier (Netdev Foundation) (2):
  selftests: drv-net: ynl: Allow cross-compiling ynl and associated
    tools
  selftests: drv-net: Use cross-compilation environment for the io_uring
    check

 tools/net/ynl/Makefile                          | 1 +
 tools/net/ynl/generated/Makefile                | 3 ++-
 tools/net/ynl/lib/Makefile                      | 3 ++-
 tools/net/ynl/tests/Makefile                    | 2 +-
 tools/net/ynl/ynltool/Makefile                  | 4 ++--
 tools/testing/selftests/drivers/net/hw/Makefile | 3 +++
 6 files changed, 11 insertions(+), 5 deletions(-)

-- 
2.55.0