The patch titled mn10300: includecheck fix: mn10300, pci.h has been added to the -mm tree. Its filename is mn10300-includecheck-fix-mn10300-pcih.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find out what to do about this The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: mn10300: includecheck fix: mn10300, pci.h From: Jaswinder Singh Rajput <jaswinder@xxxxxxxxxx> Fix the following 'make includecheck' warning: arch/mn10300/include/asm/pci.h: linux/mm.h is included more than once. Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@xxxxxxxxx> Signed-off-by: David Howells <dhowells@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- arch/mn10300/include/asm/pci.h | 1 - 1 file changed, 1 deletion(-) diff -puN arch/mn10300/include/asm/pci.h~mn10300-includecheck-fix-mn10300-pcih arch/mn10300/include/asm/pci.h --- a/arch/mn10300/include/asm/pci.h~mn10300-includecheck-fix-mn10300-pcih +++ a/arch/mn10300/include/asm/pci.h @@ -59,7 +59,6 @@ void pcibios_penalize_isa_irq(int irq); #include <linux/slab.h> #include <asm/scatterlist.h> #include <linux/string.h> -#include <linux/mm.h> #include <asm/io.h> struct pci_dev; _ Patches currently in -mm which might be from jaswinder@xxxxxxxxxx are origin.patch linux-next.patch kernel-core-add-smp_call_function_any.patch arch-x86-kernel-cpu-cpufreq-acpi-cpufreqc-avoid-cross-cpu-interrupts-by-using-smp_call_function_any.patch gitignore-usr-initramfs_datacpiobz2-and-usr-initramfs_datacpiolzma.patch mn10300-includecheck-fix-mn10300-pcih.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