From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Stephen Hemminger <stephen@networkplumber.org>,
Gagandeep Singh <G.Singh@nxp.com>,
"Sachin Saxena (OSS)" <sachin.saxena@oss.nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: Bus scan is too chatty
Date: Mon, 11 Nov 2024 09:36:09 +0000 [thread overview]
Message-ID: <PAXPR04MB93283BC666EDF4642F48DB3889582@PAXPR04MB9328.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <12313176.VV5PYv0bhD@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Monday, November 11, 2024 3:02 PM
> To: Stephen Hemminger <stephen@networkplumber.org>; Gagandeep Singh
> <G.Singh@nxp.com>; Sachin Saxena (OSS) <sachin.saxena@oss.nxp.com>;
> Hemant Agrawal <hemant.agrawal@nxp.com>
> Cc: dev@dpdk.org
> Subject: Re: Bus scan is too chatty
> Importance: High
>
> 10/11/2024 20:17, Stephen Hemminger:
> > 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.
>
> When merging the recent fslmc patches, I've reduced the verbosity of some
> fslmc logs appearing at the cleanup stage.
>
> This log is from EAL because fslmc scan fails.
> It should not return an error if there is no bus or no environment variable.
>
> Sachin, Hemant, please could you fix it?
>
[Hemant] yes, let me have a look and provide a fix.
next prev parent reply other threads:[~2024-11-11 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 19:17 Stephen Hemminger
2024-11-11 9:32 ` Thomas Monjalon
2024-11-11 9:36 ` Hemant Agrawal [this message]
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=PAXPR04MB93283BC666EDF4642F48DB3889582@PAXPR04MB9328.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.com \
--cc=G.Singh@nxp.com \
--cc=dev@dpdk.org \
--cc=sachin.saxena@oss.nxp.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).