From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [RFC][PATCH] powerpc/pci: Pull ppc32 code we need in ppc64
Date: Fri, 29 May 2009 17:18:44 +1000 [thread overview]
Message-ID: <1243581524.17903.34.camel@pasglop> (raw)
In-Reply-To: <1242803331.16901.188.camel@pasglop>
On Wed, 2009-05-20 at 17:08 +1000, Benjamin Herrenschmidt wrote:
> On Wed, 2009-05-20 at 00:57 -0500, Kumar Gala wrote:
> > Ben,
> >
> > Comments on the pmac case?
>
> Not yet :-) Give me a day. Was tracking a bug today.
A few days later...
Looks good. I had a quick peek at powermac users of the early ops and
they all seem to have a valid "hose".
Cheers,
Ben.
prev parent reply other threads:[~2009-05-29 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 20:49 [RFC][PATCH] powerpc/pci: Pull ppc32 code we need in ppc64 Kumar Gala
2009-05-20 5:57 ` Kumar Gala
2009-05-20 7:08 ` Benjamin Herrenschmidt
2009-05-29 7:18 ` Benjamin Herrenschmidt [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=1243581524.17903.34.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).