The patch titled
drivers/usb/serial/ti_usb_3410_5052.c: ti_usb returns EIO when reopening the device
has been removed from the -mm tree. Its filename was
drivers-usb-serial-ti_usb_3410_5052c-ti_usb-returns-eio-when-reopening-the-device.patch
This patch was dropped because an alternative patch was merged
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: drivers/usb/serial/ti_usb_3410_5052.c: ti_usb returns EIO when reopening the device
From: Christoph Mair <christoph.mair@xxxxxxxxx>
Fix regression introduced by 4a90f09b20f4622dcbff1f0e1e6bae1704f8ad8c
("tty: usb-serial krefs").
The driver works as expected until you close the device and try to reopen
it. All you get from now on, is an I/O error. It seems that something
isn't released correctly, because the refcount of the usbserial module
does not drop to zero, even when unloading all dependent drivers.
Cc: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
Cc: Greg KH <greg@xxxxxxxxx>
Cc: <stable@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/usb/serial/ti_usb_3410_5052.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/usb/serial/ti_usb_3410_5052.c~drivers-usb-serial-ti_usb_3410_5052c-ti_usb-returns-eio-when-reopening-the-device drivers/usb/serial/ti_usb_3410_5052.c
--- a/drivers/usb/serial/ti_usb_3410_5052.c~drivers-usb-serial-ti_usb_3410_5052c-ti_usb-returns-eio-when-reopening-the-device
+++ a/drivers/usb/serial/ti_usb_3410_5052.c
@@ -1218,8 +1218,8 @@ static void ti_bulk_in_callback(struct u
tport->tp_icount.rx += urb->actual_length;
spin_unlock(&tport->tp_lock);
}
- tty_kref_put(tty);
}
+ tty_kref_put(tty);
exit:
/* continue to read unless stopping */
_
Patches currently in -mm which might be from christoph.mair@xxxxxxxxx are
drivers-usb-serial-ti_usb_3410_5052c-ti_usb-returns-eio-when-reopening-the-device.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
