From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, ppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: linux-next: build failure
Date: Thu, 16 Oct 2008 09:11:49 -0700 [thread overview]
Message-ID: <48F767C5.8000207@goop.org> (raw)
In-Reply-To: <20081016103916.GA30745@elte.hu>
Ingo Molnar wrote:
> * Stephen Rothwell <sfr@canb.auug.org.au> 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
next prev parent reply other threads:[~2008-10-16 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 9:29 linux-next: build failure Stephen Rothwell
2008-10-16 10:39 ` Ingo Molnar
2008-10-16 16:11 ` Jeremy Fitzhardinge [this message]
2008-10-16 16:14 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2009-04-08 4:04 Stephen Rothwell
2009-04-08 5:12 ` Alan Modra
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=48F767C5.8000207@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--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).