From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: mmlnx@us.ibm.com, netdev@vger.kernel.org
Subject: Re: [PATCH] e1000e: io_error_detected callback should return PCI_ERS_RESULT_DISCONNECT on permanent failure
Date: Mon, 01 Jun 2009 18:26:51 -0700 (PDT) [thread overview]
Message-ID: <20090601.182651.227000394.davem@davemloft.net> (raw)
In-Reply-To: <9929d2390906011643q3967535cue22345e6a40a4b14@mail.gmail.com>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Mon, 1 Jun 2009 16:43:39 -0700
> On Fri, May 29, 2009 at 2:16 PM, Mike Mason <mmlnx@us.ibm.com> wrote:
>> PCI drivers that implement the io_error_detected callback
>> should return PCI_ERS_RESULT_DISCONNECT if the state
>> passed in is pci_channel_io_perm_failure. This state is not checked in many
>> of the network drivers.
>>
>> This patch fixes the omission in the e1000e driver.
>>
>> Signed-off-by: Mike Mason <mmlnx@us.ibm.com>
>> --- a/drivers/net/e1000e/netdev.c 2009-05-23 14:47:00.000000000 -0700
>> +++ b/drivers/net/e1000e/netdev.c 2009-05-29 13:43:24.000000000 -0700
>> @@ -4616,6 +4616,9 @@ static pci_ers_result_t e1000_io_error_d
>>
>> netif_device_detach(netdev);
>>
>> + if (state == pci_channel_io_perm_failure)
>> + return PCI_ERS_RESULT_DISCONNECT;
>> +
>> if (netif_running(netdev))
>> e1000e_down(adapter);
>> pci_disable_device(pdev);
>>
>> --
>
> Looks good.
>
> Acked-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Jeff, can you simply queue this up into the next batch of Intel
driver bits you send to me?
Thanks!
prev parent reply other threads:[~2009-06-02 1:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 21:16 [PATCH] e1000e: io_error_detected callback should return PCI_ERS_RESULT_DISCONNECT on permanent failure Mike Mason
2009-06-01 23:43 ` Jeff Kirsher
2009-06-02 1:26 ` David Miller [this message]
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=20090601.182651.227000394.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=mmlnx@us.ibm.com \
--cc=netdev@vger.kernel.org \
/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).