From: Stephen Hemminger <stephen@networkplumber.org>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: "Morten Brørup" <mb@smartsharesystems.com>, dev@dpdk.org
Subject: Re: [PATCH 3/3] drivers: always enable the null net driver [RFC]
Date: Thu, 22 Jan 2026 08:09:21 -0800 [thread overview]
Message-ID: <20260122080921.1f06d6af@phoenix.local> (raw)
In-Reply-To: <aXI7STpuEtMWQloB@bricha3-mobl1.ger.corp.intel.com>
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.
next prev parent reply other threads:[~2026-01-22 16:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 12:23 [PATCH 0/3] manage net/null dependency for tests Bruce Richardson
2026-01-22 12:23 ` [PATCH 1/3] test/bpf: skip some testing if null net driver not present Bruce Richardson
2026-01-22 16:19 ` Stephen Hemminger
2026-01-22 16:23 ` Bruce Richardson
2026-01-22 22:17 ` [PATCH] test/bpf: skip the BPF ELF load tests if net null missing Stephen Hemminger
2026-01-23 7:55 ` Morten Brørup
2026-02-16 14:58 ` David Marchand
2026-01-22 12:23 ` [PATCH 2/3] test: fix missing dependency on null networking driver Bruce Richardson
2026-01-22 12:23 ` [PATCH 3/3] drivers: always enable the null net driver [RFC] Bruce Richardson
2026-01-22 13:13 ` Morten Brørup
2026-01-22 13:31 ` Bruce Richardson
2026-01-22 13:40 ` Morten Brørup
2026-01-22 14:59 ` Bruce Richardson
2026-01-22 16:09 ` Stephen Hemminger [this message]
2026-01-22 13:47 ` David Marchand
2026-01-22 14:57 ` Bruce Richardson
2026-01-22 15:37 ` Morten Brørup
2026-02-19 17:39 ` [PATCH v2 0/4] improve net/null dependency handling for tests Bruce Richardson
2026-02-19 17:39 ` [PATCH v2 1/4] test/event_eth_rx_adapter: skip tests if no ethdevs Bruce Richardson
2026-02-19 17:39 ` [PATCH v2 2/4] test/event_eth_tx_adapter: remove dependency on NULL PMD Bruce Richardson
2026-02-19 17:39 ` [PATCH v2 3/4] test: fix missing dependency on null networking driver Bruce Richardson
2026-02-19 17:39 ` [PATCH v2 4/4] build/tests: add warning for missing NULL PMD dependency Bruce Richardson
2026-02-19 19:44 ` [PATCH v2 0/4] improve net/null dependency handling for tests Morten Brørup
2026-03-03 16:29 ` David Marchand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260122080921.1f06d6af@phoenix.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox