All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob <jerinj@marvell.com>
Cc: dev@dpdk.org, olivier.matz@6wind.com, jerinj@marvell.com
Subject: Re: [dpdk-dev] [PATCH] bus/pci: set boot-up log prints to absolute minimum
Date: Thu, 06 Feb 2020 15:14:21 +0100	[thread overview]
Message-ID: <5378505.1B3tZ46Xf9@xps> (raw)
In-Reply-To: <20200121080021.2835490-1-jerinj@marvell.com>

21/01/2020 09:00, jerinj@marvell.com:
> From: Jerin Jacob <jerinj@marvell.com>
> 
> Some machines may have a lot of PCI devices, logs from PCI probe
> creates a lot of clutter on boot-up, typically one needs
> to scroll the screen to find other issues in boot-up.
> 
> This patch changes the loglevel of PCI probes to `debug`
> to reduce the clutter on default boot-up logs

I think the PCI probe informations are... informational.
Maybe you are just not interested in info logs.
If this is the case, I suggest to change the log level at runtime.




  reply	other threads:[~2020-02-06 14:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21  8:00 [dpdk-dev] [PATCH] bus/pci: set boot-up log prints to absolute minimum jerinj
2020-02-06 14:14 ` Thomas Monjalon [this message]
2020-02-06 14:36   ` Jerin Jacob
2020-04-25 20:12     ` Thomas Monjalon
2020-04-26 17:42       ` Jerin Jacob
2020-04-26 18:06         ` Thomas Monjalon
2020-04-26 18:48           ` Jerin Jacob
2020-04-26 19:56             ` Thomas Monjalon
2020-04-27 18:02               ` Jerin Jacob
2020-05-04 13:26 ` [dpdk-dev] [PATCH v2] " jerinj
2020-05-07 13:54   ` Jerin Jacob
2020-05-07 15:36     ` Thomas Monjalon
2020-05-11 14:39       ` Thomas Monjalon

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=5378505.1B3tZ46Xf9@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=olivier.matz@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.