public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: [git pull] Input updates for v6.8-rc7
Date: Thu, 7 Mar 2024 21:40:31 -0800	[thread overview]
Message-ID: <Zeqhkk0HJwEIUZ0D@google.com> (raw)

Hi Linus,

Please pull from:

	git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git tags/input-for-v6.8-rc7

to receive updates for the input subsystem. You will get:

- a revert of endpoint checks in bcm5974 - the driver is being naughty
  and pokes at unclaimed USB interface, so the check fails. We need to
  fix the driver to claim both interfaces, and then re-implement the
  endpoints check

- a fix to Synaptics RMI driver to avoid UAF on driver unload or device
  unbinding

- a few new VID/PIDs added to xpad game controller driver

- a change to gpio_keys_polled driver to quiet it when GPIO causes probe
  deferral.

Changelog:
---------

Javier Carrasco (1):
      Revert "Input: bcm5974 - check endpoint type before starting traffic"

Mathias Krause (1):
      Input: synaptics-rmi4 - fix UAF of IRQ domain on driver removal

Max Nguyen (1):
      Input: xpad - add additional HyperX Controller Identifiers

Uwe Kleine-König (1):
      Input: gpio_keys_polled - suppress deferred probe error for gpio

Diffstat:
--------

 drivers/input/joystick/xpad.c             |  6 ++++++
 drivers/input/keyboard/gpio_keys_polled.c | 10 ++++------
 drivers/input/mouse/bcm5974.c             | 20 --------------------
 drivers/input/rmi4/rmi_driver.c           |  6 +++---
 4 files changed, 13 insertions(+), 29 deletions(-)

Thanks.


-- 
Dmitry

             reply	other threads:[~2024-03-08  5:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08  5:40 Dmitry Torokhov [this message]
2024-03-08 22:28 ` [git pull] Input updates for v6.8-rc7 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=Zeqhkk0HJwEIUZ0D@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox