From: Arnd Bergmann <arnd@arndb.de>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: mach-shmobile: fix platsmp.c build when ARCH_SH73A0=n
Date: Fri, 06 Jul 2012 15:35:51 +0000 [thread overview]
Message-ID: <201207061535.51239.arnd@arndb.de> (raw)
In-Reply-To: <20120706082005.30495.53308.sendpatchset@w520>
On Friday 06 July 2012, Simon Horman wrote:
> On Fri, Jul 06, 2012 at 05:20:05PM +0900, Magnus Damm wrote:
> > From: Magnus Damm <damm@opensource.se>
> >
> > Fix build error in the case of SMP=y but ARCH_SH73A0=n
> > introduced by:
> >
> > 9601e87 ARM: shmobile: fix smp build
> >
> > The use of of_machine_is_compatible() will link in the
> > the SoC-specific symbols:
> > "sh73a0_get_core_count", "sh73a0_smp_prepare_cpus",
> > "sh73a0_secondary_init" and "sh73a0_boot_secondary".
> >
> > This patch adds an ugly #ifdef wrapper as a stop-gap
> > solution.
>
> I will be happier once we have a more permanent solution :^)
That should not take too long. Marc Zyngier has posted a number
of versions of his SMP abstraction that will remove the need
for the multiplexer.
> > Signed-off-by: Magnus Damm <damm@opensource.se>
>
> Tested-by: Simon Horman <horms@verge.net.au>
>
It can actually be written a little nicer now, like
#define is_sh73a0() (machine_is_ag5evm() || machine_is_kota2() || \
(IS_ENABLED(CONFIG_ARCH_SH73A0) && \
of_machine_is_compatible("renesas,sh73a0")))
but that won't work for the backport and it's still a little
ugly.
Arnd
next prev parent reply other threads:[~2012-07-06 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 8:20 [PATCH] ARM: mach-shmobile: fix platsmp.c build when ARCH_SH73A0=n Magnus Damm
2012-07-06 10:03 ` Simon Horman
2012-07-06 15:35 ` Arnd Bergmann [this message]
2012-07-06 18:40 ` Rafael J. Wysocki
2012-07-06 20:02 ` Arnd Bergmann
2012-07-06 20:32 ` Rafael J. Wysocki
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=201207061535.51239.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-sh@vger.kernel.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