From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: David Brown <davidb@codeaurora.org>,
Randy Dunlap <rdunlap@xenotime.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Jun 7 (fs / block / rcu)
Date: Thu, 7 Jun 2012 21:07:15 -0700 [thread overview]
Message-ID: <20120608040715.GA868@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120607223107.GA21150@sirena.org.uk>
On Thu, Jun 07, 2012 at 11:31:07PM +0100, Mark Brown wrote:
> On Thu, Jun 07, 2012 at 01:00:07PM -0700, David Brown wrote:
> > On Thu, Jun 07, 2012 at 09:58:07AM -0700, Randy Dunlap wrote:
>
> > net/built-in.o:/home/davidb/upstream/kdev/kernel/include/linux/rcupdate.h:312: more undefined references to `rcu_is_cpu_idle' follow
>
> This is because rcu_is_cpu_idle() is only defined if PROVE_RCU but it's
> used in a bunch of other cases.
The following should clear it up, please accept my apologies for the
hassle.
Thanx, Paul
------------------------------------------------------------------------
rcu: Fix rcu_is_cpu_idle() #ifdef in TINY_RCU
The rcu_is_cpu_idle() function is used if CONFIG_DEBUG_LOCK_ALLOC,
but TINY_RCU defines it only when CONFIG_PROVE_RCU. This causes
build failures when CONFIG_DEBUG_LOCK_ALLOC=y but CONFIG_PROVE_RCU=n.
This commit therefore adjusts the #ifdefs for rcu_is_cpu_idle() so
that it is defined when CONFIG_DEBUG_LOCK_ALLOC=y.
Signed-off-by: Paul E. McKenney <paul.mckenney@linaro.org>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
diff --git a/kernel/rcutiny.c b/kernel/rcutiny.c
index 37a5444..547b1fe 100644
--- a/kernel/rcutiny.c
+++ b/kernel/rcutiny.c
@@ -172,7 +172,7 @@ void rcu_irq_enter(void)
local_irq_restore(flags);
}
-#ifdef CONFIG_PROVE_RCU
+#ifdef CONFIG_DEBUG_LOCK_ALLOC
/*
* Test whether RCU thinks that the current CPU is idle.
@@ -183,7 +183,7 @@ int rcu_is_cpu_idle(void)
}
EXPORT_SYMBOL(rcu_is_cpu_idle);
-#endif /* #ifdef CONFIG_PROVE_RCU */
+#endif /* #ifdef CONFIG_DEBUG_LOCK_ALLOC */
/*
* Test whether the current CPU was interrupted from idle. Nested
next prev parent reply other threads:[~2012-06-08 4:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 3:18 linux-next: Tree for Jun 7 Stephen Rothwell
2012-06-07 16:30 ` linux-next: Tree for Jun 7 (staging/ccg) Randy Dunlap
2012-06-07 16:33 ` linux-next: Tree for Jun 7 (mfd/twl6040-irq) Randy Dunlap
2012-06-07 17:53 ` Samuel Ortiz
2012-06-07 16:58 ` linux-next: Tree for Jun 7 (fs / block / rcu) Randy Dunlap
2012-06-07 20:00 ` David Brown
2012-06-07 22:31 ` Mark Brown
2012-06-08 4:07 ` Paul E. McKenney [this message]
2012-06-07 20:08 ` linux-next: Tree for Jun 7 (staging/ccg #2) Randy Dunlap
2012-06-07 20:59 ` Alan Stern
2012-06-11 8:44 ` Andrzej Pietrasiewicz
2012-06-11 9:07 ` [PATCH 1/2] staging: usb: gadget: Configurable Composite Gadget depends on BLOCK Andrzej Pietrasiewicz
2012-06-11 9:11 ` [PATCH 1/2 RESEND] " Andrzej Pietrasiewicz
2012-06-12 16:17 ` Randy Dunlap
2012-06-11 9:13 ` [PATCH 2/2] drivers: usb: gadget: add multiple definition guards Andrzej Pietrasiewicz
2012-06-12 16:17 ` Randy Dunlap
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=20120608040715.GA868@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=davidb@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/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