Re: [PATCH 3/3] drivers: always enable the null net driver [RFC]

Stephen Hemminger
2026-01-22T16:09:29Z

On Thu, 22 Jan 2026 14:59:21 +0000
Bruce Richardson <bruce.richardson@intel.com> wrote:

>
> > Then I'll suggest an alternative to this patch:
> > Change the fast-test application, so it emits an informational message about which tests are being skipped because the net/null driver is missing.
> >
> That is sadly non-trivial, and if we do so for net-null, we should also do
> so for a bunch of other components where we disable tests if they are
> missing. But the idea of just informing the user rather than force-enabling
> the driver is a good one.

I am ok with either of three solutions:
- require it to be always enabled
- in meson.build, add dependency on net_null for tests that need it.
(that is what my patches did)
- add per test checks for vdev_init failing and return TEST_SKIPPED
There also is unsupported status, but that doesn't appear to be used
or work right

Doing dependency at build time is my preference.