From mboxrd@z Thu Jan 1 00:00:00 1970 From: linux@arm.linux.org.uk (Russell King - ARM Linux) Date: Thu, 2 May 2013 19:54:49 +0100 Subject: Latest build results - errors/warnings - lots of them In-Reply-To: <20130502153834.GR28721@atomide.com> References: <20130430081739.GP14496@n2100.arm.linux.org.uk> <20130502082218.GA21614@n2100.arm.linux.org.uk> <20130502153834.GR28721@atomide.com> Message-ID: <20130502185449.GD21614@n2100.arm.linux.org.uk> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, May 02, 2013 at 08:38:34AM -0700, Tony Lindgren wrote: > * Russell King - ARM Linux [130502 01:27]: > > On Tue, Apr 30, 2013 at 09:17:39AM +0100, Russell King - ARM Linux wrote: > > > Latest nightly build of 3.9+my for-next+arm-soc's for-next results in a > > > great load of new warnings and errors. arch/arm/common/mcpm_head.S, > > > arch/arm/common/mcpm_platsmp.c, arch/arm/common/vlock.S are the biggest > > > source of errors. > > > > > > OMAP stuff needs a serious look at too - much Kconfig madness there > > > caused by over-use of select, which then goes on to cause build errors > > > because it assumes some stuff is always enabled. > > > > > > There's also warnings about of_device_id from include/linux/of_platform.h > > > via from arch/arm/kernel/setup.c which feature in all the non-OF builds > > > too which need addressing. > > > > > > See todays http://www.arm.linux.org.uk/developer/build/ results for all > > > the details and configs. Not pushing my tree until some of this stuff > > > gets fixed. > > > > And now we have a new bunch of warnings from OMAP stuff which weren't > > previously there... > > > > arch/arm/mach-omap2/omap_device.c: In function 'omap_device_get_by_hwmod_name': > > arch/arm/mach-omap2/omap_device.c:821:3: warning: return makes pointer from integer without a cast > > arch/arm/mach-omap2/omap_device.c:826:3: warning: return makes pointer from integer without a cast > > Hmm these I already fixed earlier along with a merge resolution, and > I'm not seeing them in next/master or arm-soc/for-next. What do you > have merged into your current tree? I just found the cause, and it's my cleanup branch. Odd that it only started appearing a couple of days ago. Should now be fixed.