[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1253747995.6110.5.camel@concordia>
Date: Thu, 24 Sep 2009 09:19:55 +1000
From: Michael Ellerman <michael@...erman.id.au>
To: Ingo Molnar <mingo@...e.hu>
Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
linux-kernel@...r.kernel.org, linuxppc-dev@...abs.org,
Paul Mackerras <paulus@...ba.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH] perf_event, powerpc: Fix compilation after big
perf_counter rename
On Wed, 2009-09-23 at 14:44 +0200, Ingo Molnar wrote:
> * Michael Ellerman <michael@...erman.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.
Yep that looks more or less normal.
> 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?
Not really, it sends mails to me, but it doesn't have a way to filter
them by branch. I think the plan is we'll keep an eye on it and either
send you patches or at least let you know that it's broken.
cheers
Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)
Powered by blists - more mailing lists