From: Linas Vepstas <linas@austin.ibm.com>
To: linux-kernel@vger.kernel.org, linuxppc64-dev@lists.linuxppc.org,
paulus@samba.org, paulus@au1.ibm.com
Cc: linas@linas.org
Subject: Remail: [PATCH] 2.6 PPC64: PCI Config Space reads need EEH checking
Date: Wed, 21 Jul 2004 16:26:21 -0500 [thread overview]
Message-ID: <20040721212621.GZ13171@austin.ibm.com> (raw)
Hi,
Here's another patch that was blocked by the email gateways.
--linas
----- Forwarded message from Mail Delivery System <Mailer-Daemon@bilge> -----
------ This is a copy of the message, including all the headers. ------
Return-path: <linas@bilge>
Received: from linas by bilge with local (Exim 3.36 #1 (Debian))
id 1Bj4LA-0005nR-00; Fri, 09 Jul 2004 17:59:36 -0500
Date: Fri, 9 Jul 2004 17:59:36 -0500
To: paulus@au1.ibm.com, paulus@samba.org
Cc: linuxppc64-dev@lists.linuxppc.org, linux-kernel@vger.kernel.org
Subject: [PATCH] 2.6 PPC64: PCI Config Space reads need EEH checking
Message-ID: <20040709225936.GH17333@bilge>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040523i
From: Linas Vepstas <linas@bilge>
Paul,
This patch adds explicit checking for EEH slot isolation events into the
PCI config space read path. The change itself would have been minor,
except that pci config reads don't have a pointer to a struct pci_dev.
Thus, I had to restructure the eeh code to accomodate this, which
seems to be a good thing anyway, making it a tad cleaner. This patch
presumes the earlier patches i.e. the notifier-call chain patch) have
been applied.
Please forward upstream if all's OK.
Signed-off-by: Linas Vepstas <linas@linas.org>
--linas
----- End forwarded message -----
next reply other threads:[~2004-07-21 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 21:26 Linas Vepstas [this message]
2004-07-22 20:31 ` Paul Mackerras
2004-07-22 21:50 ` Linas Vepstas
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=20040721212621.GZ13171@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linas@linas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@lists.linuxppc.org \
--cc=paulus@au1.ibm.com \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®