From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: socfpga: fix build break for allyesconfig
Date: Fri, 26 Oct 2012 21:26:49 +0000 [thread overview]
Message-ID: <201210262126.49201.arnd@arndb.de> (raw)
In-Reply-To: <1351289861-16297-1-git-send-email-dinguyen@altera.com>
On Friday 26 October 2012, dinguyen at altera.com wrote:
> ENTRY(secondary_trampoline)
> +#if __LINUX_ARM_ARCH__ >= 7
> movw r0, #:lower16:CPU1_START_ADDR
> movt r0, #:upper16:CPU1_START_ADDR
> +#endif
I don't think this is the right fix, because it will break
running on SMP socfpga machines if you enable both socfpga
and picoxcell in a multiplatform configuration.
Arnd
next prev parent reply other threads:[~2012-10-26 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 22:17 [PATCH] arm: socfpga: fix build break for allyesconfig dinguyen at altera.com
2012-10-26 21:26 ` Arnd Bergmann [this message]
2012-10-26 21:51 ` Russell King - ARM Linux
2012-10-26 22:36 ` Pavel Machek
2012-10-26 22:43 ` Russell King - ARM Linux
2012-10-26 23:00 ` Pavel Machek
2012-10-27 10:43 ` Arnd Bergmann
2012-10-27 11:24 ` Pavel Machek
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=201210262126.49201.arnd@arndb.de \
--to=arnd@arndb.de \
--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).