From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, laijs@cn.fujitsu.com,
dipankar@in.ibm.com, akpm@linux-foundation.org,
mathieu.desnoyers@polymtl.ca, josht@linux.vnet.ibm.com,
dvhltc@us.ibm.com, niv@us.ibm.com, tglx@linutronix.de,
peterz@infradead.org, rostedt@goodmis.org,
Paul Mundt <lethal@linux-sh.org>
Subject: Re: [PATCH -tip 0/2] Temporary RCU fixes for notrace and hotplug CPU
Date: Tue, 25 Aug 2009 11:41:57 -0700 [thread overview]
Message-ID: <20090825184157.GK6616@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090825181907.GC3277@elte.hu>
On Tue, Aug 25, 2009 at 08:19:07PM +0200, Ingo Molnar wrote:
>
> * Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
>
> > On Tue, Aug 25, 2009 at 08:55:01AM +0200, Ingo Molnar wrote:
> > >
> > > FYI, -tip testing found a new build warning on SH caused by the RCU
> > > tree (i suspect this warning triggers on other architectures as
> > > well):
> > >
> > > /home/mingo/tip/kernel/rcutree.c:88: warning: '__rcu_offline_cpu'
> > > declared 'static' but never defined
> >
> > <red face>
> >
> > > it's harmless, but since we are generally trying to fix all warnings
> > > and gravitate towards more and more -Werror subsystems, it would be
> > > nice to fix this.
> >
> > Indeed, and I have updated my build-output-check script to alert
> > me to warning messages from my multiple-configuration test runs.
> > Please see below for patch.
>
> btw., you can unset CONFIG_ALLOW_WARNINGS in -tip kernels to turn
> build warnings into build failures - and those are harder to miss.
Thank you for the tip!!!
Thanx, Paul
next prev parent reply other threads:[~2009-08-25 18:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 16:41 [PATCH -tip 0/2] Temporary RCU fixes for notrace and hotplug CPU Paul E. McKenney
2009-08-24 16:42 ` [PATCH -tip 1/2] Add "notrace" to RCU function headers used by ftrace Paul E. McKenney
2009-08-24 23:38 ` Steven Rostedt
2009-08-25 0:10 ` Mathieu Desnoyers
2009-08-25 2:02 ` Paul E. McKenney
2009-08-25 2:11 ` Steven Rostedt
2009-08-25 2:25 ` Paul E. McKenney
2009-08-25 7:13 ` [tip:core/rcu] rcu: " tip-bot for Paul E. McKenney
2009-08-24 16:42 ` [PATCH -tip 2/2] Add CPU-offline processing for single-node configurations Paul E. McKenney
2009-08-25 7:13 ` [tip:core/rcu] rcu: " tip-bot for Paul E. McKenney
2009-08-25 6:55 ` [PATCH -tip 0/2] Temporary RCU fixes for notrace and hotplug CPU Ingo Molnar
2009-08-25 8:00 ` Ingo Molnar
2009-08-25 16:12 ` Paul E. McKenney
2009-08-25 16:25 ` Mathieu Desnoyers
2009-08-25 17:11 ` Paul E. McKenney
2009-08-25 18:02 ` Mathieu Desnoyers
2009-08-25 18:36 ` [PATCH -tip] " Paul E. McKenney
2009-08-26 0:53 ` Lai Jiangshan
2009-08-26 1:31 ` Paul E. McKenney
2009-08-25 15:40 ` Paul E. McKenney
2009-08-25 18:19 ` Ingo Molnar
2009-08-25 18:41 ` Paul E. McKenney [this message]
2009-08-25 18:21 ` [tip:core/rcu] rcu: Add #ifdef to suppress __rcu_offline_cpu() warning in !HOTPLUG_CPU builds tip-bot for Paul E. McKenney
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=20090825184157.GK6616@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dipankar@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=josht@linux.vnet.ibm.com \
--cc=laijs@cn.fujitsu.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--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.