From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: imx: select HAVE_IMX_SRC when SMP is enabled
Date: Thu, 17 Jan 2013 12:48:03 +0200 [thread overview]
Message-ID: <1358419683.2731.220.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1350977942-15964-1-git-send-email-shawn.guo@linaro.org>
On Tue, 2012-10-23 at 15:39 +0800, Shawn Guo wrote:
> With being part of multi-platform support, SMP can be enabled by other
> platform even when SOC_IMX6Q is deselected. It leads to a situation
> that arch/arm/mach-imx/platsmp.c is built without HAVE_IMX_SRC selection
> which will cause build error. For example, the following link errors
> will be seen when building imx5 with other v7 platforms.
>
> arch/arm/mach-imx/built-in.o: In function `imx_cpu_die':
> platform-ahci-imx.c:(.text+0x219c): undefined reference to `imx_enable_cpu'
> arch/arm/mach-imx/built-in.o: In function `imx_boot_secondary':
> platform-ahci-imx.c:(.cpuinit.text+0x14): undefined reference to `imx_set_cpu_jump'
> platform-ahci-imx.c:(.cpuinit.text+0x20): undefined reference to `imx_enable_cpu'
>
> Select HAVE_IMX_SRC as long as SMP is enabled to fix the problem.
>
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
The build is still broken in Linus' tree...
--
Best Regards,
Artem Bityutskiy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130117/91f7f5e2/attachment.sig>
next prev parent reply other threads:[~2013-01-17 10:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 7:39 [PATCH] ARM: imx: select HAVE_IMX_SRC when SMP is enabled Shawn Guo
2013-01-17 10:48 ` Artem Bityutskiy [this message]
2013-01-17 10:52 ` Artem Bityutskiy
2013-01-17 10:56 ` Shawn Guo
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=1358419683.2731.220.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.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).