Subject: Re: linux-next: build failure

From: Jeremy Fitzhardinge <[email-masked]>
Date: Thu, 16 Oct 2008 09:11:49 -0700

Ingo Molnar wrote:
> * Stephen Rothwell <[email-masked]> wrote:
>
>   
>> Hi all,
>>
>> Today's linux-next build (powerpc allyesconfig) failed like this:
>>
>> In file included from arch/powerpc/include/asm/mmu-hash64.h:17,
>>                  from arch/powerpc/include/asm/mmu.h:8,
>>                  from arch/powerpc/include/asm/pgtable.h:8,
>>                  from arch/powerpc/mm/slb.c:20:
>> arch/powerpc/include/asm/page.h:76: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'memstart_addr'
>> arch/powerpc/include/asm/page.h:77: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'kernstart_addr'
>>
>> Caused by commit 600715dcdf567c86f8b2c6173fcfb4b873e25a19 ("generic: add
>> phys_addr_t for holding physical addresses") from the tip-core tree.
>> This only fails if CONFIG_RELOCATABLE is set.
>>
>> I have applied the patch below.
>>     
>
> applied to tip/core/urgent, thanks Stephen!
>   

Shouldn't this go via a ppc tree?  Won't having ppc changes in tip.git 
make people grumpy?

    J