From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: Bus scan is too chatty
Date: Sun, 10 Nov 2024 11:17:50 -0800 [thread overview]
Message-ID: <20241110111750.015ac026@hermes.local> (raw)
DPDK EAL needs to be less verbose for non-existent buses.
Most users won't have embedded devices, and messages like:
EAL: Scan for (fslmc) bus failed.
will be confusing.
next reply other threads:[~2024-11-10 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 19:17 Stephen Hemminger [this message]
2024-11-11 9:32 ` Thomas Monjalon
2024-11-11 9:36 ` Hemant Agrawal
2024-11-12 17:35 ` Patrick Robb
2024-11-12 18:19 ` Ferruh Yigit
2024-11-12 18:28 ` Patrick Robb
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=20241110111750.015ac026@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
/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;
as well as URLs for NNTP newsgroup(s).