All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>
Subject: [GIT PULL] HID for 5.9
Date: Mon, 10 Aug 2020 11:29:10 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.YFH.7.76.2008101127040.27422@cbobk.fhfr.pm> (raw)

Linus,

please pull from

  git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git for-linus

to receive HID subsystem updates for 5.9. Highlights:

=====
- fix for some modern devices that return multi-byte battery report, 
  from Grant Likely
- fix for devices with Resolution Multiplier, from Peter Hutterer
- device probing speed increase, from Dmitry Torokhov
- ThinkPad 10 Ultrabook Keyboard support, from Hans de Goede
- other small assorted fixes and device ID additions
=====

Thanks.

----------------------------------------------------------------
Alexander A. Klimov (3):
      HID: mcp2221: Replace HTTP links with HTTPS ones
      HID: udraw-ps3: Replace HTTP links with HTTPS ones
      HID: Replace HTTP links with HTTPS ones

Colin Ian King (1):
      HID: usbhid: remove redundant assignment to variable retval

Daniel G. Morse (1):
      HID: Wiimote: Treat the d-pad as an analogue stick

Dmitry Torokhov (1):
      HID: usbhid: do not sleep when opening device

Grant Likely (1):
      HID: input: Fix devices that return multiple bytes in battery report

Hans de Goede (6):
      HID: lenovo: Merge tpkbd and cptkbd data structures
      HID: lenovo: Factor out generic parts of the LED code
      HID: lenovo: Rename fn_lock sysfs attr handlers to make them generic
      HID: lenovo: Add ThinkPad 10 Ultrabook Keyboard support
      HID: lenovo: Add ThinkPad 10 Ultrabook Keyboard fn_lock support
      HID: lenovo: Fix spurious F23 key press report during resume from suspend

Ikjoon Jang (1):
      HID: quirks: add NOGET quirk for Logitech GROUP

Kai-Heng Feng (1):
      HID: intel-ish-hid: Replace PCI_DEV_FLAGS_NO_D3 with pci_save_state

Peter Hutterer (1):
      HID: input: do not run GET_REPORT unless there's a Resolution Multiplier

 drivers/hid/Kconfig                     |   2 +-
 drivers/hid/hid-cp2112.c                |   2 +-
 drivers/hid/hid-ids.h                   |   2 +
 drivers/hid/hid-input.c                 |  36 ++--
 drivers/hid/hid-lenovo.c                | 360 +++++++++++++++++++++++++-------
 drivers/hid/hid-mcp2221.c               |   2 +-
 drivers/hid/hid-quirks.c                |   1 +
 drivers/hid/hid-udraw-ps3.c             |   2 +-
 drivers/hid/hid-wiimote-core.c          |   5 +
 drivers/hid/hid-wiimote-modules.c       |  67 +++---
 drivers/hid/hid-wiimote.h               |   2 +
 drivers/hid/intel-ish-hid/ipc/pci-ish.c |  16 +-
 drivers/hid/usbhid/hid-core.c           |  55 ++---
 drivers/hid/usbhid/usbhid.h             |   2 +
 14 files changed, 404 insertions(+), 150 deletions(-)

-- 
Jiri Kosina
SUSE Labs


             reply	other threads:[~2020-08-10  9:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10  9:29 Jiri Kosina [this message]
2020-08-10 23:40 ` [GIT PULL] HID for 5.9 pr-tracker-bot

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=nycvar.YFH.7.76.2008101127040.27422@cbobk.fhfr.pm \
    --to=jikos@kernel.org \
    --cc=benjamin.tissoires@redhat.com \
    --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.