The patch titled parport: parport_serial, don't bind netmos ibm 0299 has been removed from the -mm tree. Its filename was parport-parport_serial-dont-bind-netmos-ibm-0299.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: parport: parport_serial, don't bind netmos ibm 0299 From: Jiri Slaby <jirislaby@xxxxxxxxx> Since netmos 9835 with subids 0x1014(IBM):0x0299 is now bound with serial/8250_pci, because it has no parallel ports and subdevice id isn't in the expected form, return -ENODEV from probe function. This is performed in netmos preinit_hook. Signed-off-by: Jiri Slaby <jirislaby@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/parport/parport_serial.c | 5 +++++ 1 file changed, 5 insertions(+) diff -puN drivers/parport/parport_serial.c~parport-parport_serial-dont-bind-netmos-ibm-0299 drivers/parport/parport_serial.c --- a/drivers/parport/parport_serial.c~parport-parport_serial-dont-bind-netmos-ibm-0299 +++ a/drivers/parport/parport_serial.c @@ -64,6 +64,11 @@ struct parport_pc_pci { static int __devinit netmos_parallel_init(struct pci_dev *dev, struct parport_pc_pci *card, int autoirq, int autodma) { + /* the rule described below doesn't hold for this device */ + if (dev->device == PCI_DEVICE_ID_NETMOS_9835 && + dev->subsystem_vendor == PCI_VENDOR_ID_IBM && + dev->subsystem_device == 0x0299) + return -ENODEV; /* * Netmos uses the subdevice ID to indicate the number of parallel * and serial ports. The form is 0x00PS, where <P> is the number of _ Patches currently in -mm which might be from jirislaby@xxxxxxxxx are origin.patch linux-next.patch pci-quirks-dont-mark-one-netmos-as-class-other.patch tty-pty-lookup-retval-fixup.patch reiser4.patch shrink_slab-handle-bad-shrinkers.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