From: paulmck@linux.vnet.ibm.com (Paul E. McKenney)
To: linux-arm-kernel@lists.infradead.org
Subject: Build error on kernel/rcutree.c
Date: Sun, 13 Jan 2013 10:12:45 -0800 [thread overview]
Message-ID: <20130113181245.GK3384@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAOMZO5ASEY6iHQ1UekR88vWZPutsJdiEuGkpsC2Civ6ezi2NGg@mail.gmail.com>
On Sun, Jan 13, 2013 at 04:03:24PM -0200, Fabio Estevam wrote:
> Hi Paul,
>
> When building ARM imx_v4_v5_defconfig the following error shows up on
> linux-next 20130111:
>
> kernel/rcutree.c:808:2: error: implicit declaration of function
> 'rcu_jiffies_till_stall_check' [-Werror=implicit-function-declaration]
> kernel/rcutree.c:941:6: error: 'rcu_cpu_stall_suppress' undeclared
> (first use in this function)
>
> Is this a known issue?
Yes, the fix is in -rcu and should make it to -next soon.
In the meantime, you can work around the problem by avoiding selecting
CONFIG_TREE_PREEMPT_RCU=y on SMP=n builds -- use CONFIG_TINY_PREEMPT_RCU
instead.
Thanx, Paul
prev parent reply other threads:[~2013-01-13 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 18:03 Build error on kernel/rcutree.c Fabio Estevam
2013-01-13 18:12 ` Paul E. McKenney [this message]
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=20130113181245.GK3384@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-arm-kernel@lists.infradead.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 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).