From: Paul Mackerras <paulus@samba.org>
To: Linas Vepstas <linas@austin.ibm.com>
Cc: linux-kernel@vger.kernel.org, linuxppc64-dev@lists.linuxppc.org,
linas@linas.org
Subject: Re: Remail: [PATCH] 2.6 PPC64: PCI Config Space reads need EEH checking
Date: Thu, 22 Jul 2004 16:31:58 -0400 [thread overview]
Message-ID: <16640.9278.416147.515293@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20040721212621.GZ13171@austin.ibm.com>
Linas Vepstas writes:
> 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 -----
-ENOPATCH :)
Paul.
next prev parent reply other threads:[~2004-07-22 20:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 21:26 Linas Vepstas
2004-07-22 20:31 ` Paul Mackerras [this message]
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=16640.9278.416147.515293@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=linas@austin.ibm.com \
--cc=linas@linas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@lists.linuxppc.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®