From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: David Brown <davidb@codeaurora.org>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: linux-next: Tree for Jun 7 (fs / block / rcu)
Date: Thu, 7 Jun 2012 23:31:07 +0100 [thread overview]
Message-ID: <20120607223107.GA21150@sirena.org.uk> (raw)
In-Reply-To: <20120607200007.GA3352@codeaurora.org>
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.
next prev parent reply other threads:[~2012-06-07 22:31 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 [this message]
2012-06-08 4:07 ` Paul E. McKenney
2012-06-07 20:08 ` linux-next: Tree for Jun 7 (staging/ccg #2) Randy Dunlap
2012-06-07 20:59 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1206071646360.1185-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
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=20120607223107.GA21150@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=davidb@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).