From: Danny Feng <dfeng@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: john.ronciak@intel.com, peter.p.waskiewicz.jr@intel.com,
bruce.w.allan@intel.com, jesse.brandeburg@intel.com,
jeffrey.t.kirsher@intel.com, e1000-devel@lists.sourceforge.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] e1000e: fix use of pci_enable_pcie_error_reporting
Date: Thu, 13 Aug 2009 12:29:39 +0800 [thread overview]
Message-ID: <4A8396B3.6090609@redhat.com> (raw)
In-Reply-To: <20090812.204621.87530668.davem@davemloft.net>
On 08/13/2009 11:46 AM, David Miller wrote:
> From: Xiaotian Feng<dfeng@redhat.com>
> Date: Fri, 7 Aug 2009 17:36:14 +0800
>
>> commit 111b9dc5 introduces pcie aer support for e1000e, but it is not
>> reasonable to disable it in e1000_remove but enable it in e1000_resume.
>> This patch enables aer support in e1000_probe.
>>
>> Signed-off-by: Xiaotian Feng<dfeng@redhat.com>
>
> In moving this block of code, you've corrupted the indentation,
> making it more indented than it should be.
>
> In any event, I expect the Intel folks to pick this up.
Yes, I agree.... but each time I resume from suspend or rmmod e1000e,
there's a warning message like "pci_enable_pcie_error_reporting failed
0xfffffffb". Since some devices may not support aer, why not silence
this kind of warning?
modprobe e1000e everything is as usual, but then rmmod e1000e, we'll see
"pci_disable_pcie_error_reporting failed 0xfffffffb", it is so weird...
>
>> diff --git a/drivers/net/e1000e/netdev.c b/drivers/net/e1000e/netdev.c
>> index 63415bb..e2f0304 100644
>> --- a/drivers/net/e1000e/netdev.c
>> +++ b/drivers/net/e1000e/netdev.c
>> @@ -4670,14 +4670,6 @@ static int e1000_resume(struct pci_dev *pdev)
>> return err;
>> }
>>
>> - /* AER (Advanced Error Reporting) hooks */
>> - err = pci_enable_pcie_error_reporting(pdev);
>> - if (err) {
>> - dev_err(&pdev->dev, "pci_enable_pcie_error_reporting failed "
>> - "0x%x\n", err);
>> - /* non-fatal, continue */
>> - }
>> -
>> pci_set_master(pdev);
>>
>> pci_enable_wake(pdev, PCI_D3hot, 0);
>> @@ -4990,6 +4982,14 @@ static int __devinit e1000_probe(struct pci_dev *pdev,
>> if (err)
>> goto err_pci_reg;
>>
>> + /* AER (Advanced Error Reporting) hooks */
>> + err = pci_enable_pcie_error_reporting(pdev);
>> + if (err) {
>> + dev_err(&pdev->dev, "pci_enable_pcie_error_reporting failed "
>> + "0x%x\n", err);
>> + /* non-fatal, continue */
>> + }
>> +
>> pci_set_master(pdev);
>> /* PCI config space info */
>> err = pci_save_state(pdev);
>> --
>> 1.6.2.5
>>
WARNING: multiple messages have this Message-ID (diff)
From: Danny Feng <dfeng@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
bruce.w.allan@intel.com, jesse.brandeburg@intel.com,
linux-kernel@vger.kernel.org, john.ronciak@intel.com,
jeffrey.t.kirsher@intel.com
Subject: Re: [PATCH] e1000e: fix use of pci_enable_pcie_error_reporting
Date: Thu, 13 Aug 2009 12:29:39 +0800 [thread overview]
Message-ID: <4A8396B3.6090609@redhat.com> (raw)
In-Reply-To: <20090812.204621.87530668.davem@davemloft.net>
On 08/13/2009 11:46 AM, David Miller wrote:
> From: Xiaotian Feng<dfeng@redhat.com>
> Date: Fri, 7 Aug 2009 17:36:14 +0800
>
>> commit 111b9dc5 introduces pcie aer support for e1000e, but it is not
>> reasonable to disable it in e1000_remove but enable it in e1000_resume.
>> This patch enables aer support in e1000_probe.
>>
>> Signed-off-by: Xiaotian Feng<dfeng@redhat.com>
>
> In moving this block of code, you've corrupted the indentation,
> making it more indented than it should be.
>
> In any event, I expect the Intel folks to pick this up.
Yes, I agree.... but each time I resume from suspend or rmmod e1000e,
there's a warning message like "pci_enable_pcie_error_reporting failed
0xfffffffb". Since some devices may not support aer, why not silence
this kind of warning?
modprobe e1000e everything is as usual, but then rmmod e1000e, we'll see
"pci_disable_pcie_error_reporting failed 0xfffffffb", it is so weird...
>
>> diff --git a/drivers/net/e1000e/netdev.c b/drivers/net/e1000e/netdev.c
>> index 63415bb..e2f0304 100644
>> --- a/drivers/net/e1000e/netdev.c
>> +++ b/drivers/net/e1000e/netdev.c
>> @@ -4670,14 +4670,6 @@ static int e1000_resume(struct pci_dev *pdev)
>> return err;
>> }
>>
>> - /* AER (Advanced Error Reporting) hooks */
>> - err = pci_enable_pcie_error_reporting(pdev);
>> - if (err) {
>> - dev_err(&pdev->dev, "pci_enable_pcie_error_reporting failed "
>> - "0x%x\n", err);
>> - /* non-fatal, continue */
>> - }
>> -
>> pci_set_master(pdev);
>>
>> pci_enable_wake(pdev, PCI_D3hot, 0);
>> @@ -4990,6 +4982,14 @@ static int __devinit e1000_probe(struct pci_dev *pdev,
>> if (err)
>> goto err_pci_reg;
>>
>> + /* AER (Advanced Error Reporting) hooks */
>> + err = pci_enable_pcie_error_reporting(pdev);
>> + if (err) {
>> + dev_err(&pdev->dev, "pci_enable_pcie_error_reporting failed "
>> + "0x%x\n", err);
>> + /* non-fatal, continue */
>> + }
>> +
>> pci_set_master(pdev);
>> /* PCI config space info */
>> err = pci_save_state(pdev);
>> --
>> 1.6.2.5
>>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
next prev parent reply other threads:[~2009-08-13 4:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 9:36 [PATCH] e1000e: fix use of pci_enable_pcie_error_reporting Xiaotian Feng
2009-08-07 9:36 ` Xiaotian Feng
2009-08-13 3:46 ` David Miller
2009-08-13 4:29 ` Danny Feng [this message]
2009-08-13 4:29 ` Danny Feng
2009-08-13 4:54 ` Jeff Kirsher
2009-08-13 23:00 ` 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=4A8396B3.6090609@redhat.com \
--to=dfeng@redhat.com \
--cc=bruce.w.allan@intel.com \
--cc=davem@davemloft.net \
--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=netdev@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 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.