Hi Uwe, On Wed, Oct 17, 2012 at 01:54:20PM +0200, Uwe Kleine-König wrote: > Hello, > > On Wed, Oct 17, 2012 at 07:36:10PM +0800, Fengguang Wu wrote: > > Hi Uwe, > > > > FYI, kernel build failed on > Thanks for testing. > > > tree: git://git.pengutronix.de/git/ukl/linux efm32 > > head: ace35988f9089852b4d7278442ead682fb1fe7a7 > > commit: 304b1a8cda3ba8a550a9b2568e027d09bbf65829 [14/19] HACK! make stack dumps provoked by BUG a bit more helpful > > config: arm-imx_v6_v7_defconfig # make ARCH=arm imx_v6_v7_defconfig > > > > All error/warnings: > > > > arch/arm/kernel/built-in.o: In function `show_regs': > > io.c:(.text+0x12b8): undefined reference to `unwind_backtrace' > I'm quite aware that commit 304b1a8cd is bad. That's why it's prefixed > with "HACK!". Also even if you can compile a kernel with > > e97f732 HACK! ARM: no, we don't enter in ARM > > it won't run on anything because it changes how the kernel must be > entered. Yeah, the title made it obvious that it's not serious. My build system is just blindly testing every branches in the tree.. > I don't know why you picked the efm32 branch of my tree, but note that > obviously it is not meant to be included in mainline as is. If you want > to do some testing, better pick my for-next branch. OK, I'll limit the tests to your for-next branch. Thanks, Fengguang -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html