Re: [PATCH] [RFC] omap: 3630: default cpu_is_omap3630 to zero

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Nishanth Menon <menon.nishanth@xxxxxxxxx> [091013 03:44]:
> Shilimkar, Santosh said the following on 10/13/2009 05:03 AM:
> > Has anybody tried building latest linux-omap master ? The build is breaking for other OMAP processors.
> >
> > CC      arch/arm/mach-omap2/id.o
> > arch/arm/mach-omap2/id.c: In function 'omap3_cpuinfo':
> > arch/arm/mach-omap2/id.c:269: error: implicit declaration of function 'cpu_is_omap3630'
> > make[1]: *** [arch/arm/mach-omap2/id.o] Error 1
> > make: *** [arch/arm/mach-omap2] Error 2
> >
> > This is because of " 0a9b95f21995aa3cdda82ebc6e77b0b2ab401861"
> > 	omap: Introduce OMAP3630
> >
> > Below patch from Vikram fixes the build break.
> >   
> ouch.. my bad.. thanks for answering my question. I am guessing we need
> this coz of is_omap3630() translation..
> Ack for the patch from me.

To me it looks like all the 35x defines need the same treatment.

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux