The patch titled kbuild: fix detection of CONFIG_FRAME_WARN=0 has been removed from the -mm tree. Its filename was kbuild-fix-detection-of-config_frame_warn=0.patch This patch was dropped because it was merged into mainline or a subsystem tree The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: kbuild: fix detection of CONFIG_FRAME_WARN=0 From: Mike Frysinger <vapier@xxxxxxxxxx> The checking of CONFIG_FRAME_WARN in the top level Makefile forgot to actually derefence the variable thus leading to an always true check. Signed-off-by: Mike Frysinger <vapier@xxxxxxxxxx> Cc: Andi Kleen <ak@xxxxxxx> Cc: Sam Ravnborg <sam@xxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN Makefile~kbuild-fix-detection-of-config_frame_warn=0 Makefile --- a/Makefile~kbuild-fix-detection-of-config_frame_warn=0 +++ a/Makefile @@ -533,7 +533,7 @@ endif include $(srctree)/arch/$(SRCARCH)/Makefile -ifneq (CONFIG_FRAME_WARN,0) +ifneq ($(CONFIG_FRAME_WARN),0) KBUILD_CFLAGS += $(call cc-option,-Wframe-larger-than=${CONFIG_FRAME_WARN}) endif _ Patches currently in -mm which might be from vapier@xxxxxxxxxx are origin.patch shm-fix-unused-warnings-on-nommu.patch linux-next.patch pcmcia-yenta-add-missing-__devexit-marking.patch drivers-hvc-add-missing-__devexit_p.patch plat_nand-add-missing-__devexit_p.patch irda-new-blackfin-on-chip-sir-irda-driver.patch virtio_blk-add-missing-__devinitexit-markings.patch kmap_types-make-most-arches-use-generic-header-file.patch gitignore-ignore-patch-files.patch drivers-char-rtc-disable-legacy-rtc-driver-on-blackfin-systems.patch gpio-max7301-add-missing-__devexit-marking.patch istallion-add-missing-__devexit-marking.patch edac-add-missing-__devexit_p.patch cramfs-move-cramfs-magic-out-of-cramfs_fsh.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html