From: xuwei5@hisilicon.com (Wei Xu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: hisi: depend on ARCH_MULTI_V7
Date: Tue, 30 Sep 2014 09:25:37 +0800 [thread overview]
Message-ID: <542A0691.8030505@hisilicon.com> (raw)
In-Reply-To: <7470114.dOWIKLTLOQ@wuerfel>
On 2014/9/29 23:46, Arnd Bergmann wrote:
> hisi has a general dependency on ARCH_MULTIPLATFORM, which is
> problematic when building a kernel for non-V7 platforms but selecting
> drivers that might conflict with other architecture levels.
>
> In this case, it broke my (still out of tree) patch set that
> enables V7M multiplatform support, since that does not enable
> MULTI_IRQ support:
>
> arch/arm/kernel/built-in.o: In function `set_handle_irq':
> arch/arm/kernel/irq.c:125: undefined reference to `handle_arch_irq'
> arch/arm/kernel/built-in.o: In function `setup_arch':
> arch/arm/kernel/setup.c:965: undefined reference to `handle_arch_irq'
>
> Since all hisilicon platforms are ARMv7 based, we can avoid this
> problem by just making the dependency more specific.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
Hi Arnd,
> I'd like to apply this patch directly to the arm-soc tree
Thanks!
Best Regards,
Wei
>
> diff --git a/arch/arm/mach-hisi/Kconfig b/arch/arm/mach-hisi/Kconfig
> index 075772b34e80..cd19433f76d3 100644
> --- a/arch/arm/mach-hisi/Kconfig
> +++ b/arch/arm/mach-hisi/Kconfig
> @@ -1,6 +1,6 @@
> config ARCH_HISI
> bool "Hisilicon SoC Support"
> - depends on ARCH_MULTIPLATFORM
> + depends on ARCH_MULTI_V7
> select ARM_AMBA
> select ARM_GIC
> select ARM_TIMER_SP804
>
>
>
prev parent reply other threads:[~2014-09-30 1:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 15:46 [PATCH] ARM: hisi: depend on ARCH_MULTI_V7 Arnd Bergmann
2014-09-30 1:25 ` Wei Xu [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=542A0691.8030505@hisilicon.com \
--to=xuwei5@hisilicon.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