From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: [patch 00/14] Current 4xx patch series
Date: Fri, 03 Aug 2007 08:38:16 +1000 [thread overview]
Message-ID: <1186094296.5495.638.camel@localhost.localdomain> (raw)
In-Reply-To: <20070802163951.11c398ee@weaponx.rchland.ibm.com>
On Thu, 2007-08-02 at 16:39 -0500, Josh Boyer wrote:
>
> Someone brought up the fact that the EMAC rewrite is mostly just
> changing probing code and the guts are still similar to the current
> EMAC driver. I haven't really looked into it yet, but if that's true,
> I'd be curious as to why it was done that way.
Ask :-) What specifically do you want to know ?
Ben.
next prev parent reply other threads:[~2007-08-02 22:38 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 ` [patch 00/14] Current 4xx patch series Hollis Blanchard
2007-08-02 21:39 ` Josh Boyer
2007-08-02 22:38 ` Benjamin Herrenschmidt [this message]
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=1186094296.5495.638.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=hollisb@us.ibm.com \
--cc=jwboyer@linux.vnet.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 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).