From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: Please pull 'for-2.6.26' branch of 4xx tree
Date: Wed, 16 Apr 2008 22:50:47 +1000 [thread overview]
Message-ID: <1208350247.6958.283.camel@pasglop> (raw)
In-Reply-To: <20080416073139.7f56e72c@zod.rchland.ibm.com>
On Wed, 2008-04-16 at 07:31 -0500, Josh Boyer wrote:
> On Wed, 16 Apr 2008 07:27:58 -0500
> Josh Boyer <jwboyer@linux.vnet.ibm.com> wrote:
>
> > On Tue, 15 Apr 2008 10:27:04 -0500
> > Josh Boyer <jwboyer@linux.vnet.ibm.com> wrote:
> >
> > > Valentine Barshak (2):
> > > [POWERPC] ibm_newemac: PowerPC 440GX EMAC PHY clock workaround
> > > [POWERPC] ibm_newemac: PowerPC 440EP/440GR EMAC PHY clock workaround
> >
> > These two commits have been dropped from the branch. They cause the
> > allyesconfig build for powerpc to fail because CONFIG_PPC_DCR_MMIO
> > doesn't understand the dcri_clrset macro.
>
> Crap. Looks like you already pulled the tree. We need to either
> revert those two commits, or essentially define dcri_clrset to a do {}
> while(0) in include/asm-powerpc/dcr-mmio.h so things build.
Why ? It should do the right thing, not nop ...
Ben.
next prev parent reply other threads:[~2008-04-16 12:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 15:27 Please pull 'for-2.6.26' branch of 4xx tree Josh Boyer
2008-04-16 12:27 ` Josh Boyer
2008-04-16 12:31 ` Josh Boyer
2008-04-16 12:50 ` Benjamin Herrenschmidt [this message]
2008-04-16 13:43 ` Josh Boyer
2008-04-16 14:02 ` Benjamin Herrenschmidt
2008-04-16 14:02 ` Josh Boyer
-- strict thread matches above, loose matches on Subject: below --
2008-06-11 11:48 Josh Boyer
2008-05-19 14:48 Josh Boyer
2008-05-06 19:57 Josh Boyer
2008-04-06 12:41 Josh Boyer
2008-03-27 12:24 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=1208350247.6958.283.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-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;
as well as URLs for NNTP newsgroup(s).