From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.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: Thu, 1 Oct 2009 09:42:01 +0200 [thread overview]
Message-ID: <20091001074201.GA6300@elte.hu> (raw)
In-Reply-To: <20090925095841.8578073a.sfr@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Ingo,
>
> On Thu, 24 Sep 2009 23:25:55 +1000 Michael Ellerman <michael@ellerman.id.au> wrote:
> >
> > 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.
>
> In the mean time I don't now if someone has pointed you at these today:
>
> http://kisskb.ellerman.id.au/kisskb/branch/12/
That's an upstream warning.
-tip supports fail-on-build-warnings build mode (for the whole kernel)
via the CONFIG_ALLOW_WARNINGS .config setting. So if you do allnoconfig
builds, make sure you turn on CONFIG_ALLOW_WARNINGS=y to get the same
build behavior as with Linus's tree.
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: michael@ellerman.id.au, 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, 1 Oct 2009 09:42:01 +0200 [thread overview]
Message-ID: <20091001074201.GA6300@elte.hu> (raw)
In-Reply-To: <20090925095841.8578073a.sfr@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Ingo,
>
> On Thu, 24 Sep 2009 23:25:55 +1000 Michael Ellerman <michael@ellerman.id.au> wrote:
> >
> > 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.
>
> In the mean time I don't now if someone has pointed you at these today:
>
> http://kisskb.ellerman.id.au/kisskb/branch/12/
That's an upstream warning.
-tip supports fail-on-build-warnings build mode (for the whole kernel)
via the CONFIG_ALLOW_WARNINGS .config setting. So if you do allnoconfig
builds, make sure you turn on CONFIG_ALLOW_WARNINGS=y to get the same
build behavior as with Linus's tree.
Ingo
next prev parent reply other threads:[~2009-10-01 7:42 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
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 [this message]
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=20091001074201.GA6300@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=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
--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.