From: David Miller <davem@davemloft.net>
To: somnath.kotur@emulex.com
Cc: netdev@vger.kernel.org, kalesh.purayil@emulex.com
Subject: Re: [PATCH net 2/2] be2net: Fix crash on 2nd invocation of PCI AER/EEH error_detected hook
Date: Thu, 30 May 2013 16:58:37 -0700 (PDT) [thread overview]
Message-ID: <20130530.165837.906560952023831713.davem@davemloft.net> (raw)
In-Reply-To: <43df230c-ad73-414a-8de0-2c4f9a5f3d71@CMEXHTCAS1.ad.emulex.com>
From: Somnath Kotur <somnath.kotur@emulex.com>
Date: Thu, 30 May 2013 14:26:17 +0530
> During a PCI EEH/AER error recovery flow, if the device did not successfully
> restart, the error_detected() hook may be called a second time with a
> "perm_failure" state. This patch skips over driver cleanup for the second
> invocation of the callback.
>
> Also, Lancer error recovery code is fixed-up to handle these changes.
>
> Signed-off-by: Kalesh AP <kalesh.purayil@emulex.com>
> Signed-off-by: Somnath kotur <somnath.kotur@emulex.com>
Applied.
prev parent reply other threads:[~2013-05-30 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 8:56 [PATCH net 2/2] be2net: Fix crash on 2nd invocation of PCI AER/EEH error_detected hook Somnath Kotur
2013-05-30 23:58 ` 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=20130530.165837.906560952023831713.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kalesh.purayil@emulex.com \
--cc=netdev@vger.kernel.org \
--cc=somnath.kotur@emulex.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;
as well as URLs for NNTP newsgroup(s).