From: Jiri Kosina <jikos@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] HID fixes
Date: Mon, 7 Nov 2016 11:01:15 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.00.1611071055410.29400@cbobk.fhfr.pm> (raw)
Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-linus
to receive -rc fixes for HID subsystem:
=====
- modprobe-after-rmmod load failure bugfix for intel-ish, from Even Xu
- IRQ probing bugfix for intel-ish, from Srinivas Pandruvada
- attribute parsing fix in hid-sensor, from Ooi, Joyce
- other small misc fixes / quirky device additions
=====
Thanks!
----------------------------------------------------------------
Borislav Petkov (1):
HID: intel-ish-hid: Fix !CONFIG_PM build warning
Even Xu (3):
HID: intel-ish-hid: consolidate ish wake up operation
HID: intel-ish-hid: Move DMA disable code to new function
HID: intel-ish-hid: Fix driver reinit failure
Oliver Neukum (1):
HID: usbhid: add ATEN CS962 to list of quirky devices
Ooi, Joyce (1):
HID: sensor: fix attributes in HID sensor interface
Srinivas Pandruvada (2):
HID: sensor-hub: Fix packing of result buffer for feature report
HID: intel-ish-hid: request_irq failure
drivers/hid/hid-ids.h | 1 +
drivers/hid/hid-sensor-custom.c | 6 +-
drivers/hid/hid-sensor-hub.c | 15 ++++-
drivers/hid/intel-ish-hid/ipc/ipc.c | 102 +++++++++++++++++++++++---------
drivers/hid/intel-ish-hid/ipc/pci-ish.c | 6 +-
drivers/hid/usbhid/hid-quirks.c | 1 +
6 files changed, 95 insertions(+), 36 deletions(-)
--
Jiri Kosina
SUSE Labs
next reply other threads:[~2016-11-07 10:01 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 10:01 Jiri Kosina [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-15 12:38 [GIT PULL] HID fixes Jiri Kosina
2024-02-15 19:50 ` pr-tracker-bot
2023-12-12 22:51 Jiri Kosina
2023-12-13 1:21 ` pr-tracker-bot
2023-11-23 19:22 Jiri Kosina
2023-11-24 1:51 ` pr-tracker-bot
2023-10-11 12:00 Benjamin Tissoires
2023-10-11 20:58 ` pr-tracker-bot
2023-10-05 20:41 Jiri Kosina
2023-10-06 3:50 ` pr-tracker-bot
2023-07-11 13:59 Benjamin Tissoires
2023-07-12 23:28 ` pr-tracker-bot
2023-06-01 10:27 Jiri Kosina
2023-06-01 21:15 ` pr-tracker-bot
2023-04-12 22:03 Jiri Kosina
2023-04-13 0:44 ` pr-tracker-bot
2023-03-09 15:07 Benjamin Tissoires
2023-03-09 19:07 ` pr-tracker-bot
2023-02-09 14:31 Benjamin Tissoires
2023-02-09 18:10 ` pr-tracker-bot
2023-01-18 20:17 Jiri Kosina
2023-01-18 22:47 ` pr-tracker-bot
2022-12-21 15:18 Benjamin Tissoires
2022-12-21 17:53 ` pr-tracker-bot
2022-11-11 10:04 Jiri Kosina
2022-11-11 18:03 ` pr-tracker-bot
2022-10-21 12:17 Benjamin Tissoires
2022-10-22 1:28 ` pr-tracker-bot
2022-08-31 10:54 Jiri Kosina
2022-08-31 17:20 ` pr-tracker-bot
2022-03-09 10:42 Jiri Kosina
2022-03-09 22:16 ` pr-tracker-bot
2022-02-15 15:35 Jiri Kosina
2022-02-15 19:19 ` pr-tracker-bot
2022-01-21 14:17 Jiri Kosina
2022-01-21 14:27 ` pr-tracker-bot
2021-12-21 14:40 Jiri Kosina
2021-12-21 17:39 ` pr-tracker-bot
2021-12-09 10:15 Jiri Kosina
2021-12-09 19:35 ` pr-tracker-bot
2021-11-24 7:10 Jiri Kosina
2021-11-24 18:31 ` pr-tracker-bot
2021-09-27 13:54 Jiri Kosina
2021-09-27 17:25 ` pr-tracker-bot
2021-07-30 12:06 Jiri Kosina
2021-07-30 18:11 ` pr-tracker-bot
2021-06-01 21:58 Jiri Kosina
2021-06-02 3:58 ` pr-tracker-bot
2021-04-15 13:51 Jiri Kosina
2021-04-15 18:15 ` pr-tracker-bot
2021-01-28 8:38 Jiri Kosina
2021-01-28 18:16 ` pr-tracker-bot
2021-01-14 12:33 Jiri Kosina
2021-01-14 21:55 ` pr-tracker-bot
2020-11-22 21:18 Jiri Kosina
2020-11-22 22:40 ` pr-tracker-bot
2020-09-02 18:58 Jiri Kosina
2020-09-02 20:08 ` pr-tracker-bot
2020-08-25 8:14 Jiri Kosina
2020-08-25 19:16 ` pr-tracker-bot
2020-07-17 12:01 Jiri Kosina
2020-07-17 17:40 ` pr-tracker-bot
2020-03-17 13:41 Jiri Kosina
2020-03-17 17:10 ` pr-tracker-bot
2020-02-27 14:46 Jiri Kosina
2020-02-27 19:40 ` pr-tracker-bot
2020-01-09 14:23 Jiri Kosina
2020-01-09 19:14 ` Linus Torvalds
2020-01-09 19:25 ` Dmitry Torokhov
2020-01-09 19:37 ` Jiri Kosina
2020-01-09 20:38 ` Jiri Kosina
2020-01-09 23:36 ` Linus Torvalds
2020-01-09 23:41 ` Linus Torvalds
2020-01-10 14:31 ` Jiri Kosina
2020-01-09 19:15 ` pr-tracker-bot
2019-11-07 19:32 Jiri Kosina
2019-11-07 20:00 ` pr-tracker-bot
2019-08-20 12:53 Jiri Kosina
2019-08-20 18:55 ` pr-tracker-bot
2019-08-06 10:59 Jiri Kosina
2019-08-06 18:55 ` pr-tracker-bot
2019-06-27 9:37 Jiri Kosina
2019-06-28 0:45 ` pr-tracker-bot
2019-04-03 13:39 Jiri Kosina
2019-04-03 16:25 ` pr-tracker-bot
2019-01-22 9:46 Jiri Kosina
2019-01-22 18:55 ` pr-tracker-bot
2018-12-10 16:05 Jiri Kosina
2018-12-10 20:20 ` pr-tracker-bot
2018-11-24 20:19 Jiri Kosina
2018-11-24 23:15 ` pr-tracker-bot
2018-11-07 10:31 Jiri Kosina
2018-11-07 17:07 ` Linus Torvalds
2018-10-03 8:55 Jiri Kosina
2018-10-03 11:50 ` Greg Kroah-Hartman
2018-09-11 7:49 Jiri Kosina
2018-07-09 12:54 Jiri Kosina
2018-06-19 12:00 Jiri Kosina
2018-06-20 1:51 ` Linus Torvalds
2018-06-20 4:19 ` Jiri Kosina
2018-06-20 7:06 ` Hans de Goede
2018-06-20 7:12 ` Linus Torvalds
2018-06-20 7:15 ` Jiri Kosina
2018-06-20 7:35 ` Benjamin Tissoires
2018-04-19 8:05 Jiri Kosina
2017-10-12 12:46 Jiri Kosina
2017-10-05 8:58 Jiri Kosina
2017-06-20 9:01 Jiri Kosina
2017-03-31 8:01 Jiri Kosina
2017-01-31 12:13 Jiri Kosina
2017-01-19 13:29 Jiri Kosina
2015-02-23 22:37 Jiri Kosina
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.00.1611071055410.29400@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.