From: Michael Ellerman <michael@ellerman.id.au>
To: Ingo Molnar <mingo@elte.hu>
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: Thu, 24 Sep 2009 23:25:55 +1000 [thread overview]
Message-ID: <1253798755.16237.4.camel@concordia> (raw)
In-Reply-To: <20090924121423.GB12262@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 1998 bytes --]
On Thu, 2009-09-24 at 14:14 +0200, Ingo Molnar wrote:
> * Michael Ellerman <michael@ellerman.id.au> wrote:
>
> > On Wed, 2009-09-23 at 14:44 +0200, Ingo Molnar wrote:
> > > * 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.
> >
> > 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.
>
> how many mails are those per day, typically? If there's not too many and
> if there's a way to send all of them to me i could post-filter them for
> -tip relevance. If that is feasible. You bouncing it to me later is
> certainly also a solution. (but lengthens the latency of fixes,
> obviously.)
Lots of mails - there are an insane number of arm configs for
starters :)
Give me a day or two, I should be able to add a per-branch setting for
who to send mails to without too much trouble.
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <michael@ellerman.id.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
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: Thu, 24 Sep 2009 23:25:55 +1000 [thread overview]
Message-ID: <1253798755.16237.4.camel@concordia> (raw)
In-Reply-To: <20090924121423.GB12262@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 1998 bytes --]
On Thu, 2009-09-24 at 14:14 +0200, Ingo Molnar wrote:
> * Michael Ellerman <michael@ellerman.id.au> wrote:
>
> > On Wed, 2009-09-23 at 14:44 +0200, Ingo Molnar wrote:
> > > * 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.
> >
> > 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.
>
> how many mails are those per day, typically? If there's not too many and
> if there's a way to send all of them to me i could post-filter them for
> -tip relevance. If that is feasible. You bouncing it to me later is
> certainly also a solution. (but lengthens the latency of fixes,
> obviously.)
Lots of mails - there are an insane number of arm configs for
starters :)
Give me a day or two, I should be able to add a per-branch setting for
who to send mails to without too much trouble.
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-09-24 13:25 UTC|newest]
Thread overview: 27+ 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-21 23:48 ` Paul Mackerras
2009-09-22 1:56 ` Benjamin Herrenschmidt
2009-09-22 1:56 ` Benjamin Herrenschmidt
2009-09-22 7:28 ` Ingo Molnar
2009-09-22 7:28 ` Ingo Molnar
2009-09-22 8:00 ` Benjamin Herrenschmidt
2009-09-22 8:00 ` Benjamin Herrenschmidt
2009-09-22 8:13 ` Ingo Molnar
2009-09-22 8:13 ` Ingo Molnar
2009-09-22 11:52 ` Michael Ellerman
2009-09-22 11:52 ` Michael Ellerman
2009-09-23 12:44 ` Ingo Molnar
2009-09-23 12:44 ` Ingo Molnar
2009-09-23 23:19 ` Michael Ellerman
2009-09-23 23:19 ` Michael Ellerman
2009-09-24 12:14 ` Ingo Molnar
2009-09-24 12:14 ` Ingo Molnar
2009-09-24 13:25 ` Michael Ellerman [this message]
2009-09-24 13:25 ` Michael Ellerman
2009-09-24 23:58 ` Stephen Rothwell
2009-09-24 23:58 ` Stephen Rothwell
2009-10-01 7:42 ` Ingo Molnar
2009-10-01 7:42 ` Ingo Molnar
2009-10-01 11:13 ` Stephen Rothwell
2009-10-01 11:13 ` Stephen Rothwell
2009-09-22 7:40 ` [tip:perf/urgent] " tip-bot for Paul Mackerras
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=1253798755.16237.4.camel@concordia \
--to=michael@ellerman.id.au \
--cc=a.p.zijlstra@chello.nl \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--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 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.