On Sun, Mar 17, 2013 at 09:33:21PM +0200, Felipe Balbi wrote: > Hi, > > On Sun, Mar 17, 2013 at 10:00:08PM +0800, Dongsheng Song wrote: > > “make ARCH=arm menuconfig” no complains, but "make ARCH=arm > > CROSS_COMPILE=arm-linux-gnueabihf-" failed: > > > > $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- > > CHK include/generated/uapi/linux/version.h > > CHK include/generated/utsrelease.h > > make[1]: `include/generated/mach-types.h' is up to date. > > CALL scripts/checksyscalls.sh > > CHK include/generated/compile.h > > CHK kernel/config_data.h > > Kernel: arch/arm/boot/Image is ready > > Kernel: arch/arm/boot/zImage is ready > > Building modules, stage 2. > > MODPOST 1904 modules > > ERROR: "flush_tlb_kernel_range" [drivers/staging/zsmalloc/zsmalloc.ko] > > undefined! > > make[1]: *** [__modpost] Error 1 > > make: *** [modules] Error 2 > > > > Please find the attachment with .config.gz file. > > linux-arm-kernel might have more information about this.
Sigh. At times, I really don't know why I bother wasting my time commenting on patches if they just go and agree with them, and promptly ignore them. I pointed out what this should be: http://marc.info/?l=linux-kernel&m=135972750522902&w=2 And it was agreed: http://marc.info/?l=linux-kernel&m=135993546317541&w=2 But for some reason the wrong patch got merged: http://marc.info/?l=git-commits-head&m=136147889001219&w=2 Maybe because it was "simpler" ? Don't know. But... well, we now know what the outcome of it was. Let's try a different technique. I'm going to say nothing of any real help and hopefully it will get fixed properly. Maybe that'll work. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
