From: Hollis Blanchard <hollisb@us.ibm.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: [patch 00/14] Current 4xx patch series
Date: Thu, 2 Aug 2007 20:57:26 +0000 (UTC) [thread overview]
Message-ID: <f8tgfm$e2g$1@sea.gmane.org> (raw)
In-Reply-To: 41060.0659474314$1184697204@news.gmane.org
On Tue, 17 Jul 2007 13:15:47 -0500, Josh Boyer wrote:
> For those interested, here's my current 4xx patch series. There are a few
> cleanups as a pre-requisite for 40x support, some minimal Walnut support, and
> another round of Bamboo patches. These are all based off of Paul's current
> tree.
Bamboo is booting for me with your patches. Let's get them in soon...
> Ethernet for 4xx in general is still provided by the out-of-tree emac rewrite
> that Ben and David have poked at. If it doesn't get merged soon, I'll take
> a look at getting it working again.
Please!
--
Hollis Blanchard
IBM Linux Technology Center
next parent reply other threads:[~2007-08-02 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41060.0659474314$1184697204@news.gmane.org>
2007-08-02 20:57 ` Hollis Blanchard [this message]
2007-08-02 21:39 ` [patch 00/14] Current 4xx patch series Josh Boyer
2007-08-02 22:38 ` Benjamin Herrenschmidt
2007-08-03 0:26 ` Josh Boyer
2007-08-03 0:29 ` Benjamin Herrenschmidt
2007-07-17 18:15 Josh Boyer
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='f8tgfm$e2g$1@sea.gmane.org' \
--to=hollisb@us.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.