From: Ingo Molnar <mingo@elte.hu>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
Paul Mackerras <paulus@samba.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] perf_event, powerpc: Fix compilation after big perf_counter rename
Date: Wed, 23 Sep 2009 14:44:20 +0200 [thread overview]
Message-ID: <20090923124420.GA5525@elte.hu> (raw)
In-Reply-To: <1253620332.10476.4.camel@concordia>
* Michael Ellerman <michael@ellerman.id.au> wrote:
> On Tue, 2009-09-22 at 18:00 +1000, Benjamin Herrenschmidt wrote:
> > On Tue, 2009-09-22 at 09:28 +0200, Ingo Molnar wrote:
> > >
> > > Nevertheless you are right that i should have caught this particular
> > > PowerPC build bug - i missed it - sorry about that!
> > >
> > Allright. Well, to help in general, we are setting up a build-bot
> > here too that will build -tip HEAD for at least powerpc daily with
> > a few configs too.
>
> Results here:
>
> http://kisskb.ellerman.id.au/kisskb/branch/12/
ok, seems green for today - the two failures are: one a powerpc
toolchain problem it appears, plus a mainline warning.
Btw., for me to be able to notice failures there it would have to email
me automatically if there's any -tip build failures that do not occur
with the upstream branch. Does it have such a feature?
Ingo
next prev parent reply other threads:[~2009-09-23 12:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 23:48 [PATCH] perf_event, powerpc: Fix compilation after big perf_counter rename Paul Mackerras
2009-09-22 1:56 ` Benjamin Herrenschmidt
2009-09-22 7:28 ` Ingo Molnar
2009-09-22 8:00 ` Benjamin Herrenschmidt
2009-09-22 8:13 ` Ingo Molnar
2009-09-22 11:52 ` Michael Ellerman
2009-09-23 12:44 ` Ingo Molnar [this message]
2009-09-23 23:19 ` Michael Ellerman
2009-09-24 12:14 ` Ingo Molnar
2009-09-24 13:25 ` Michael Ellerman
2009-09-24 23:58 ` Stephen Rothwell
2009-10-01 7:42 ` Ingo Molnar
2009-10-01 11:13 ` 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=20090923124420.GA5525@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=paulus@samba.org \
--cc=torvalds@linux-foundation.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).