Re: [PATCH] ARM: OMAP4: Fix definition of IS_PM44XX_ERRATUM

2014-03-13 Thread Tony Lindgren
* Kevin Hilman [140313 11:30]: > Nishanth Menon writes: > > > Just like IS_PM34XX_ERRATUM, IS_PM44XX_ERRATUM is valid only if > > CONFIG_PM is enabled, else, disabling CONFIG_PM results in build > > failure complaining about the following: > > arch/arm/mach-omap2/built-in.o: In function `omap4_b

Re: [PATCH] ARM: OMAP4: Fix definition of IS_PM44XX_ERRATUM

2014-03-13 Thread Kevin Hilman
Nishanth Menon writes: > Just like IS_PM34XX_ERRATUM, IS_PM44XX_ERRATUM is valid only if > CONFIG_PM is enabled, else, disabling CONFIG_PM results in build > failure complaining about the following: > arch/arm/mach-omap2/built-in.o: In function `omap4_boot_secondary': > :(.text+0x8a70): undefined

Re: [PATCH] ARM: OMAP4: Fix definition of IS_PM44XX_ERRATUM

2014-03-12 Thread Santosh Shilimkar
On Thursday 13 March 2014 06:07 AM, Nishanth Menon wrote: > On 03/12/2014 04:59 PM, Santosh Shilimkar wrote: >> On Thursday 13 March 2014 05:43 AM, Nishanth Menon wrote: >>> Just like IS_PM34XX_ERRATUM, IS_PM44XX_ERRATUM is valid only if >>> CONFIG_PM is enabled, else, disabling CONFIG_PM results i

Re: [PATCH] ARM: OMAP4: Fix definition of IS_PM44XX_ERRATUM

2014-03-12 Thread Nishanth Menon
On 03/12/2014 04:59 PM, Santosh Shilimkar wrote: > On Thursday 13 March 2014 05:43 AM, Nishanth Menon wrote: >> Just like IS_PM34XX_ERRATUM, IS_PM44XX_ERRATUM is valid only if >> CONFIG_PM is enabled, else, disabling CONFIG_PM results in build >> failure complaining about the following: >> arch/arm

Re: [PATCH] ARM: OMAP4: Fix definition of IS_PM44XX_ERRATUM

2014-03-12 Thread Santosh Shilimkar
On Thursday 13 March 2014 05:43 AM, Nishanth Menon wrote: > Just like IS_PM34XX_ERRATUM, IS_PM44XX_ERRATUM is valid only if > CONFIG_PM is enabled, else, disabling CONFIG_PM results in build > failure complaining about the following: > arch/arm/mach-omap2/built-in.o: In function `omap4_boot_seconda

[PATCH] ARM: OMAP4: Fix definition of IS_PM44XX_ERRATUM

2014-03-12 Thread Nishanth Menon
Just like IS_PM34XX_ERRATUM, IS_PM44XX_ERRATUM is valid only if CONFIG_PM is enabled, else, disabling CONFIG_PM results in build failure complaining about the following: arch/arm/mach-omap2/built-in.o: In function `omap4_boot_secondary': :(.text+0x8a70): undefined reference to `pm44xx_errata' Fixe