From: Linas Vepstas <linas@austin.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: anton@samba.org, akpm@osdl.org, linuxppc64-dev@ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PPC64: EEH Recovery
Date: Thu, 20 Jan 2005 16:48:12 -0600 [thread overview]
Message-ID: <20050120224812.GK9140@austin.ibm.com> (raw)
In-Reply-To: <16877.63693.915740.385920@cargo.ozlabs.ibm.com>
On Wed, Jan 19, 2005 at 05:06:05PM +1100, Paul Mackerras was heard to remark:
> Linas Vepstas writes:
>
> > p.s. It was not clear to me if the EEH patch previously sent
> > (6 January 2005, same subject line) will be wending its way into
> > the main Torvalds kernel tree, or not. I hadn't really gotten
> > confirmation one way or another.
>
> I'm not really totally happy with it yet, on a number of fronts:
[...]
I forgot to mention: while I agree with some/many of these points,
especially with regards to recovery, I'd also like to note that the
patch was mailed in two independent parts:
-- a number of generic infrastructure routines, all in a ppc64 patch, and
-- the code that actually performs the recovery, as a patch to
the drivers/pci/hotplug subsystem.
While the actual recovery code is controversial (e.g. no support of
scsi recovery), I'd like to at least get in the the generic
infrastructure pieces.
--linas
next prev parent reply other threads:[~2005-01-20 22:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 19:24 [PATCH] PPC64: EEH Recovery Linas Vepstas
2005-01-17 20:14 ` Linas Vepstas
2005-01-19 6:06 ` Paul Mackerras
2005-01-19 16:00 ` Nathan Fontenot
2005-01-20 22:39 ` Linas Vepstas
2005-01-21 2:50 ` Paul Mackerras
2005-01-20 22:48 ` Linas Vepstas [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-17 23:52 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=20050120224812.GK9140@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
--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