This is a note to let you know that I've just added the patch titled
[PATCH 129/135] Input: xpad - move pending clear to the correct
to the 4.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:
0129-Input-xpad-move-pending-clear-to-the-correct-locatio.patch
and it can be found in the queue-4.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 3898d97cefa00264fffcbf8d5f50f1a9c2682526 Mon Sep 17 00:00:00 2001
From: Pavel Rojtberg <rojtberg@xxxxxxxxx>
Date: Fri, 1 Jul 2016 17:32:09 -0400
Subject: [PATCH 129/135] Input: xpad - move pending clear to the correct
location
[ Upstream commit 4efc6939a83c54fb3417541be48991afd0290ba3 ]
otherwise we lose ff commands: https://github.com/paroj/xpad/issues/27
Signed-off-by: Pavel Rojtberg <rojtberg@xxxxxxxxx>
Cc: stable@xxxxxxxxxxxxxxx
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
Signed-off-by: Sasha Levin <alexander.levin@xxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/input/joystick/xpad.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/input/joystick/xpad.c
+++ b/drivers/input/joystick/xpad.c
@@ -718,6 +718,7 @@ static bool xpad_prepare_next_out_packet
if (packet) {
memcpy(xpad->odata, packet->data, packet->len);
xpad->irq_out->transfer_buffer_length = packet->len;
+ packet->pending = false;
return true;
}
@@ -757,7 +758,6 @@ static void xpad_irq_out(struct urb *urb
switch (status) {
case 0:
/* success */
- xpad->out_packets[xpad->last_out_packet].pending = false;
xpad->irq_out_active = xpad_prepare_next_out_packet(xpad);
break;
Patches currently in stable-queue which might be from rojtberg@xxxxxxxxx are
queue-4.4/0108-Input-xpad-correctly-handle-concurrent-LED-and-FF-re.patch
queue-4.4/0129-Input-xpad-move-pending-clear-to-the-correct-locatio.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