From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: More patches pushed to powerpc.git master and powerpc-next branches
Date: Wed, 16 Apr 2008 22:49:28 +1000 [thread overview]
Message-ID: <1208350168.6958.281.camel@pasglop> (raw)
In-Reply-To: <20080416224510.85e9dace.sfr@canb.auug.org.au>
On Wed, 2008-04-16 at 22:45 +1000, Stephen Rothwell wrote:
> On Wed, 16 Apr 2008 22:32:46 +1000 Paul Mackerras <paulus@samba.org> wrote:
> >
> > [POWERPC] ibm_newemac: PowerPC 440GX EMAC PHY clock workaround
> > [POWERPC] ibm_newemac: PowerPC 440EP/440GR EMAC PHY clock workaround
>
> So close :-)
The workaround for those is actually subtely different :-0
Ben.
next prev parent reply other threads:[~2008-04-16 12:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 12:32 More patches pushed to powerpc.git master and powerpc-next branches Paul Mackerras
2008-04-16 12:42 ` Paul Mackerras
2008-04-16 13:57 ` Josh Boyer
2008-04-16 12:45 ` Stephen Rothwell
2008-04-16 12:49 ` Benjamin Herrenschmidt [this message]
2008-04-16 13:52 ` 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=1208350168.6958.281.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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).