Re: [PATCH 4/8] ARM: OMAP: build mach-omap code only if needed

2013-07-08 Thread Tony Lindgren
* Arnd Bergmann [130705 09:28]: > If we build a kernel with CONFIG_ARCH_OMAP2PLUS enabled but all of the > individual SoCs disabled, we run into a large number of link errors > because if incorrect dependencies: > > arch/arm/mach-omap2/built-in.o: In function `_add_initiator_dep': > arch/arm/mach

Re: [PATCH 4/8] ARM: OMAP: build mach-omap code only if needed

2013-07-08 Thread Olof Johansson
[fixed linux-arm-kernel address] On Mon, Jul 8, 2013 at 4:31 AM, Olof Johansson wrote: > Hi, > > I think this broke multi_v7_defconfig in last night's linux-next, due > to TI_PRIV_EDMA no longer being selected. Looks like you missed it > when moving the options around: > > On Fri, Jul 5, 2013 at

Re: [PATCH 4/8] ARM: OMAP: build mach-omap code only if needed

2013-07-08 Thread Olof Johansson
Hi, I think this broke multi_v7_defconfig in last night's linux-next, due to TI_PRIV_EDMA no longer being selected. Looks like you missed it when moving the options around: On Fri, Jul 5, 2013 at 9:23 AM, Arnd Bergmann wrote: > diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconf

[PATCH 4/8] ARM: OMAP: build mach-omap code only if needed

2013-07-05 Thread Arnd Bergmann
If we build a kernel with CONFIG_ARCH_OMAP2PLUS enabled but all of the individual SoCs disabled, we run into a large number of link errors because if incorrect dependencies: arch/arm/mach-omap2/built-in.o: In function `_add_initiator_dep': arch/arm/mach-omap2/omap_hwmod.c:691: undefined reference