The patch titled add-hypertransport-capability-defines-fix has been removed from the -mm tree. Its filename is add-hypertransport-capability-defines-fix.patch This patch was dropped because it was folded into add-hypertransport-capability-defines.patch ------------------------------------------------------ Subject: add-hypertransport-capability-defines-fix From: Andrew Morton <akpm@xxxxxxxx> Eric cnat tpye. Cc: Eric W. Biederman <ebiederm@xxxxxxxxxxxx> Cc: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx> Cc: Greg KH <greg@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxx> --- include/linux/pci_regs.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN include/linux/pci_regs.h~add-hypertransport-capability-defines-fix include/linux/pci_regs.h --- a/include/linux/pci_regs.h~add-hypertransport-capability-defines-fix +++ a/include/linux/pci_regs.h @@ -14,7 +14,7 @@ * PCI System Design Guide * * For hypertransport information, please consult the following manuals - * from http://www.hypertranposrt.org + * from http://www.hypertransport.org * * The Hypertransport I/O Link Specification */ _ Patches currently in -mm which might be from akpm@xxxxxxxx are origin.patch hdrcheck-permission-fix.patch mmc-driver-for-ti-flashmedia-card-reader-source.patch ecryptfs.patch fbdev-riva-warning-fix.patch genirq-convert-the-i386-architecture-to-irq-chips.patch genirq-x86_64-irq-reenable-migrating-irqs-to-other-cpus.patch genirq-msi-simplify-msi-enable-and-disable.patch genirq-ia64-irq-dynamic-irq-support.patch genirq-msi-only-build-msi-apicc-on-ia64.patch genirq-i386-irq-remove-the-msi-assumption-that-irq-==-vector.patch genirq-x86_64-irq-make-vector_irq-per-cpu.patch add-hypertransport-capability-defines.patch add-hypertransport-capability-defines-fix.patch initial-generic-hypertransport-interrupt-support-Kconfig-fix.patch srcu-report-out-of-memory-errors-fixlet.patch git-powerpc-wrapper-dont-require-execute-permissions.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