From: timg@tpi.com (Tim Gardner)
To: jesse.brandeburg@intel.com
Cc: bruce.w.allan@intel.com, e1000-devel@lists.sourceforge.net,
jeffrey.t.kirsher@intel.com, john.ronciak@intel.com,
linux-kernel@vger.kernel.org, peter.p.waskiewicz.jr@intel.com
Subject: [PATCH] e1000e: Fix PCIE error message
Date: Wed, 30 Sep 2009 14:33:22 -0600 (MDT) [thread overview]
Message-ID: <20090930203322.E7963F88DD@sepang.rtg.net> (raw)
>From bfafcd3a39e13c3f6cedf9cc8eff2efdc9af7271 Mon Sep 17 00:00:00 2001
From: Tim Gardner <tim.gardner@canonical.com>
Date: Wed, 30 Sep 2009 14:30:08 -0600
Subject: [PATCH] e1000e: Fix PCIE error message
BugLink: http://bugs.launchpad.net/bugs/436370
The error returned by pci_enable_pcie_error_reporting() is ignored, so
print a notice instead of an error. Users tends to freak out
when they see messages like this.
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
Cc: stable@kernel.org
---
drivers/net/e1000e/netdev.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/e1000e/netdev.c b/drivers/net/e1000e/netdev.c
index 16c193a..69a761a 100644
--- a/drivers/net/e1000e/netdev.c
+++ b/drivers/net/e1000e/netdev.c
@@ -4984,7 +4984,7 @@ static int __devinit e1000_probe(struct pci_dev *pdev,
/* AER (Advanced Error Reporting) hooks */
err = pci_enable_pcie_error_reporting(pdev);
if (err) {
- dev_err(&pdev->dev, "pci_enable_pcie_error_reporting failed "
+ dev_notice(&pdev->dev, "pci_enable_pcie_error_reporting failed "
"0x%x\n", err);
/* non-fatal, continue */
}
--
1.6.2.4
next reply other threads:[~2009-09-30 20:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 20:33 Tim Gardner [this message]
2009-09-30 21:28 ` [PATCH] e1000e: Fix PCIE error message Frans Pop
2009-10-01 22:39 ` Jeff Kirsher
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=20090930203322.E7963F88DD@sepang.rtg.net \
--to=timg@tpi.com \
--cc=bruce.w.allan@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox