Hi Greg,

These are the part II commits that I've analized from the list of
upstream commits that have been backported to 3.2 but missing from 3.4.

For the 17 commits,
 - 4 commits were marked for stable but can't be applied cleanly to
   3.4.x.
 - 11 commits have no stable tag. I've found out why they were backported
   to 3.2.x, and I'm sure they should be applied to 3.4.x.
 - 2 commits dropped, because it fix a problem, but be reverted later.

Please cherry-pick these commits from 3.2.x:
01d35d12e9a7    HID: logitech: don't use stack based dj_report structures
fb1c3652bb3e    HID: hidraw: add proper error handling to raw event reporting
9c48cc08ae12    HID: fix return value of hidraw_report_event() when 
!CONFIG_HIDRAW
3313aa9015c7    HID: hidraw: fix list->buffer memleak
3084fc2f2e8c    HID: hidraw: improve error handling in hidraw_init()
fb3ea00df6b9    HID: apple: Add Apple wireless keyboard 2011 ANSI PID
3207e0076af2    HID: add support for Sony RF receiver with USB product id 0x0374
76610d6dfbe4    HID: clean up quirk for Sony RF receivers
606eea676790    HID: usbhid: quirk for MSI GX680R led panel  (cc: stable)
1f276d988f8e    HID: usbhid: fix build problem 
384a27453c74    HID: hidraw: correctly deallocate memory on device disconnect

There are 4 other commits that need some adjustments. I'll send
out the backports.

 drivers/hid/hid-apple.c         |    3 +
 drivers/hid/hid-core.c          |   26 +++++++----
 drivers/hid/hid-ids.h           |   10 ++++
 drivers/hid/hid-input.c         |   12 ++++-
 drivers/hid/hid-logitech-dj.c   |   38 ++++++++++------
 drivers/hid/hid-multitouch.c    |    4 +-
 drivers/hid/hid-sony.c          |   18 ++++++-
 drivers/hid/hidraw.c            |   98 ++++++++++++++++++++++-----------------
 drivers/hid/usbhid/hid-quirks.c |    3 +
 include/linux/hid.h             |    2 +-
 include/linux/hidraw.h          |    4 +-
 11 files changed, 144 insertions(+), 74 deletions(-)


--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to