The patch titled i386: fix another modpost warning has been removed from the -mm tree. Its filename was i386-fix-another-modpost-warning.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ Subject: i386: fix another modpost warning From: Vivek Goyal <vgoyal@xxxxxxxxxx> o MODPOST generates warning for i386 if kernel is compiled with CONFIG_RELOCATABLE=y WARNING: vmlinux - Section mismatch: reference to .init.data: from .data between 'this_cpu' (at offset 0xc05194d0) and 'cpuinfo_op' o this_cpu pointer should be of type __cpuinitdata. Signed-off-by: Vivek Goyal <vgoyal@xxxxxxxxxx> Cc: Andi Kleen <ak@xxxxxxx> Cc: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxx> --- arch/i386/kernel/cpu/common.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN arch/i386/kernel/cpu/common.c~i386-fix-another-modpost-warning arch/i386/kernel/cpu/common.c --- a/arch/i386/kernel/cpu/common.c~i386-fix-another-modpost-warning +++ a/arch/i386/kernel/cpu/common.c @@ -54,7 +54,7 @@ static struct cpu_dev __cpuinitdata defa .c_init = default_init, .c_vendor = "Unknown", }; -static struct cpu_dev * this_cpu = &default_cpu; +static struct cpu_dev * this_cpu __cpuinitdata = &default_cpu; static int __init cachesize_setup(char *str) { _ Patches currently in -mm which might be from vgoyal@xxxxxxxxxx are scsi-megaraid_mmmbox-init-fix-for-kdump.patch i386-cpu-hotplug-smpboot-misc-modpost-warning-fixes.patch convert-some-functions-to-__init-to-avoid-modpost-warnings.patch i386-move-startup_32-in-texthead-section.patch break-init-in-two-parts-to-avoid-modpost-warnings.patch i386-fix-memory-hotplug-related-modpost-generated-warning.patch i386-make-apic-probe-function-non-init.patch modpost-add-more-symbols-to-whitelist-pattern2.patch modpost-whitelist-reference-to-more-symbols-pattern-3.patch clockevents-i386-drivers.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