DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Patrick Robb <probb@iol.unh.edu>, Thomas Monjalon <thomas@monjalon.net>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	Gagandeep Singh <G.Singh@nxp.com>,
	"Sachin Saxena (OSS)" <sachin.saxena@oss.nxp.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: Re: Bus scan is too chatty
Date: Tue, 12 Nov 2024 18:19:16 +0000	[thread overview]
Message-ID: <4c30c98b-32b8-4e82-907b-962f9a88bad0@amd.com> (raw)
In-Reply-To: <CAJvnSUBJq6VGxPtUVjSTjvr9_k9aK2fE7Yk9pnJCscCgx9Xrow@mail.gmail.com>

On 11/12/2024 5:35 PM, Patrick Robb wrote:
> Hello,
> 
> I'm noting here that the compressdev test failures reported over the
> weekend for the Community Lab are related to this, as the DTS
> compressdev tests fail if EAL contains "failed." So, these patchseries
> failures can be ignored by maintainers.
> 
> I see the fix from Hemant was merged by Thomas. It looks like some of
> the recent failures are from series applied to next-net, so I'm guessing
> that branch need to be rebased on main.
> 

Hi Patrick,

I am not clear with problem, but I rebased next-net on -rc2, will this
fix the issue for you?

> Thanks.
> 
> On Mon, Nov 11, 2024 at 4:36 AM Hemant Agrawal <hemant.agrawal@nxp.com
> <mailto:hemant.agrawal@nxp.com>> wrote:
> 
> 
>     > -----Original Message-----
>     > From: Thomas Monjalon <thomas@monjalon.net
>     <mailto:thomas@monjalon.net>>
>     > Sent: Monday, November 11, 2024 3:02 PM
>     > To: Stephen Hemminger <stephen@networkplumber.org
>     <mailto:stephen@networkplumber.org>>; Gagandeep Singh
>     > <G.Singh@nxp.com <mailto:G.Singh@nxp.com>>; Sachin Saxena (OSS)
>     <sachin.saxena@oss.nxp.com <mailto:sachin.saxena@oss.nxp.com>>;
>     > Hemant Agrawal <hemant.agrawal@nxp.com
>     <mailto:hemant.agrawal@nxp.com>>
>     > Cc: dev@dpdk.org <mailto: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.
> 


  reply	other threads:[~2024-11-12 18:19 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
2024-11-12 17:35     ` Patrick Robb
2024-11-12 18:19       ` Ferruh Yigit [this message]
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=4c30c98b-32b8-4e82-907b-962f9a88bad0@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=G.Singh@nxp.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=probb@iol.unh.edu \
    --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).