From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Guenter Roeck <linux@roeck-us.net>,
Frederic Weisbecker <fweisbec@gmail.com>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
Anil Kumar <anilk4.v@gmail.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>,
Tony Lindgren <tony@atomide.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
Benoit Cousson <b-cousson@ti.com>
Subject: Re: Build error in torvalds kernel 3.11 for omap2plus
Date: Mon, 9 Sep 2013 21:31:41 +0100 [thread overview]
Message-ID: <20130909203141.GM25647@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130909160348.GB18975@roeck-us.net>
On Mon, Sep 09, 2013 at 09:03:48AM -0700, Guenter Roeck wrote:
> Unfortunately, there are more problems.
>
> arch/arm/kernel/built-in.o: In function `ret_fast_syscall':
> /home/groeck/src/linux-stable/arch/arm/kernel/entry-common.S:42: undefined reference to `user_enter'
> arch/arm/kernel/built-in.o: In function `no_work_pending':
> /home/groeck/src/linux-stable/arch/arm/kernel/entry-common.S:77: undefined reference to `user_enter'
> arch/arm/kernel/built-in.o: In function `vector_swi':
> /home/groeck/src/linux-stable/arch/arm/kernel/entry-common.S:376: undefined reference to `user_exit'
> arch/arm/kernel/built-in.o: In function `__dabt_usr':
> /home/groeck/src/linux-stable/arch/arm/kernel/entry-armv.S:365: undefined reference to `user_exit'
> arch/arm/kernel/built-in.o: In function `__irq_usr':
> /home/groeck/src/linux-stable/arch/arm/kernel/entry-armv.S:375: undefined reference to `user_exit'
> arch/arm/kernel/built-in.o: In function `__und_usr':
> /home/groeck/src/linux-stable/arch/arm/kernel/entry-armv.S:388: undefined reference to `user_exit'
> arch/arm/kernel/built-in.o: In function `__pabt_usr':
> /home/groeck/src/linux-stable/arch/arm/kernel/entry-armv.S:662: undefined reference to `user_exit'
These are due to ad65782fba50 (context_tracking: Optimize main APIs off case
with static key) converting these functions to be inline.
No idea what the fix for this is other than reverting the change. Any
ideas Frederic?
next prev parent reply other threads:[~2013-09-09 20:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-08 6:04 Build error in torvalds kernel 3.11 for omap2plus Anil Kumar
2013-09-08 9:02 ` Russell King - ARM Linux
2013-09-08 17:16 ` Guenter Roeck
2013-09-09 10:51 ` Russell King - ARM Linux
2013-09-09 12:00 ` Guenter Roeck
2013-09-09 14:24 ` Nicolas Pitre
2013-09-09 16:03 ` Guenter Roeck
2013-09-09 20:31 ` Russell King - ARM Linux [this message]
2013-09-09 21:02 ` Guenter Roeck
2013-09-09 21:16 ` Nicolas Pitre
2013-09-10 15:07 ` Kevin Hilman
2013-09-10 15:09 ` Frederic Weisbecker
2013-09-13 17:03 ` [PATCH] arm: Fix build error with context tracking calls Frederic Weisbecker
2013-09-13 22:50 ` Kevin Hilman
2013-09-14 14:19 ` Frederic Weisbecker
2013-09-16 17:11 ` Kevin Hilman
2013-09-14 14:32 ` Russell King - ARM Linux
2013-09-22 16:59 ` Frederic Weisbecker
2013-09-25 17:38 ` Kevin Hilman
2013-09-27 13:30 ` Frederic Weisbecker
2013-09-09 10:55 ` Build error in torvalds kernel 3.11 for omap2plus Anil Kumar
2013-09-09 11:30 ` Guenter Roeck
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=20130909203141.GM25647@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=anilk4.v@gmail.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=fweisbec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nicolas.pitre@linaro.org \
--cc=tony@atomide.com \
/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).