From: Aristeu Rozanski <aris@redhat.com>
To: Jiang Liu <jiang.liu@linux.intel.com>
Cc: Mauro Carvalho Chehab <m.chehab@samsung.com>,
Doug Thompson <dougthompson@xmission.com>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sb_edac: degrade log level for "EDAC sbridge: Seeking for: dev 1d.3 PCI ID xxxx"
Date: Mon, 17 Feb 2014 09:32:36 -0500 [thread overview]
Message-ID: <20140217143236.GS15457@redhat.com> (raw)
In-Reply-To: <1392613824-11230-1-git-send-email-jiang.liu@linux.intel.com>
On Mon, Feb 17, 2014 at 01:10:23PM +0800, Jiang Liu wrote:
> On a system with four Intel processor, it generates too many messages
> "EDAC sbridge: Seeking for: dev 1d.3 PCI ID xxxx". And it doesn't
> give many useful information for normal users, so change log level
> from INFO to DEBUG.
>
> Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
> ---
> drivers/edac/sb_edac.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/edac/sb_edac.c b/drivers/edac/sb_edac.c
> index 54e2abe..347c7a1 100644
> --- a/drivers/edac/sb_edac.c
> +++ b/drivers/edac/sb_edac.c
> @@ -1263,7 +1263,7 @@ static int sbridge_get_onedevice(struct pci_dev **prev,
> struct pci_dev *pdev = NULL;
> u8 bus = 0;
>
> - sbridge_printk(KERN_INFO,
> + sbridge_printk(KERN_DEBUG,
> "Seeking for: dev %02x.%d PCI ID %04x:%04x\n",
> dev_descr->dev, dev_descr->func,
> PCI_VENDOR_ID_INTEL, dev_descr->dev_id);
ACK
--
Aristeu
next prev parent reply other threads:[~2014-02-17 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 5:10 [PATCH] sb_edac: degrade log level for "EDAC sbridge: Seeking for: dev 1d.3 PCI ID xxxx" Jiang Liu
2014-02-17 14:32 ` Aristeu Rozanski [this message]
2014-02-20 10:49 ` Borislav Petkov
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=20140217143236.GS15457@redhat.com \
--to=aris@redhat.com \
--cc=dougthompson@xmission.com \
--cc=jiang.liu@linux.intel.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.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.