This is a note to let you know that I've just added the patch titled
USB: ark3116: fix control-message timeout
to the 3.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
usb-ark3116-fix-control-message-timeout.patch
and it can be found in the queue-3.4 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 634371911730a462626071065b64cd6e1fe213e0 Mon Sep 17 00:00:00 2001
From: Johan Hovold <jhovold@xxxxxxxxx>
Date: Mon, 27 May 2013 14:44:41 +0200
Subject: USB: ark3116: fix control-message timeout
From: Johan Hovold <jhovold@xxxxxxxxx>
commit 634371911730a462626071065b64cd6e1fe213e0 upstream.
The control-message timeout is specified in milliseconds and should not
depend on HZ.
Signed-off-by: Johan Hovold <jhovold@xxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/usb/serial/ark3116.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/usb/serial/ark3116.c
+++ b/drivers/usb/serial/ark3116.c
@@ -49,7 +49,7 @@ static bool debug;
#define DRIVER_NAME "ark3116"
/* usb timeout of 1 second */
-#define ARK_TIMEOUT (1*HZ)
+#define ARK_TIMEOUT 1000
static const struct usb_device_id id_table[] = {
{ USB_DEVICE(0x6547, 0x0232) },
Patches currently in stable-queue which might be from jhovold@xxxxxxxxx are
queue-3.4/usb-serial-fix-treo-kyocera-interrrupt-in-urb-context.patch
queue-3.4/usb-mos7720-fix-dma-to-stack.patch
queue-3.4/usb-iuu_phoenix-fix-bulk-message-timeout.patch
queue-3.4/usb-whiteheat-fix-broken-port-configuration.patch
queue-3.4/usb-mos7720-fix-hardware-flow-control.patch
queue-3.4/usb-keyspan-fix-bogus-array-index.patch
queue-3.4/usb-ark3116-fix-control-message-timeout.patch
queue-3.4/usb-mos7720-fix-message-timeouts.patch
queue-3.4/usb-visor-fix-initialisation-of-treo-kyocera-devices.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html