From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: tip tree build failure
Date: Mon, 24 Aug 2009 09:32:15 +0200 [thread overview]
Message-ID: <20090824073215.GA30040@elte.hu> (raw)
In-Reply-To: <1251097136.7538.124.camel@twins>
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Mon, 2009-08-24 at 16:54 +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > Today's linux-next build (powerpc ppc64_defconfig) failed like this:
> >
> > arch/powerpc/kernel/perf_callchain.c: In function 'perf_callchain_kernel':
> > arch/powerpc/kernel/perf_callchain.c:73: error: implicit declaration of function 'perf_paranoid_anon_ip'
> >
> > Caused by commit 512cec5d6f2a71e04464bf4fd76a50571bd0dea1 ("perf_counter:
> > powerpc: Support the anonimized kernel callchain bits") which I have
> > reverted for today.
>
> Yes, that needs to be gone, it relied on another change which
> never went in. Ingo could you make that commit disappear?
Correct - it's still near the tail of the tree so i zapped it.
Ingo
next prev parent reply other threads:[~2009-08-24 7:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 6:54 linux-next: tip tree build failure Stephen Rothwell
2009-08-24 6:58 ` Peter Zijlstra
2009-08-24 7:32 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-04 12:59 Stephen Rothwell
2010-01-04 16:32 ` Ingo Molnar
2010-01-05 3:39 ` Stephen Rothwell
2010-01-05 7:39 ` Pekka Enberg
2009-11-11 9:13 Stephen Rothwell
2009-11-11 15:03 ` FUJITA Tomonori
2009-11-11 21:39 ` Stephen Rothwell
2009-06-12 6:30 Stephen Rothwell
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=20090824073215.GA30040@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.