Linux Input/HID development
 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 v7.2-rc0 (part 2)
Date: Sat, 27 Jun 2026 22:11:31 -0700	[thread overview]
Message-ID: <akCs9sqkWvpJnCpK@google.com> (raw)

Hi Linus,

Please pull from:

	git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git tags/input-for-v7.2-rc0-2

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

- Updates to Synaptics RMI4 driver to fix potential OOB accesses in
  F30 and F3A keymap handling

- A workaround in Synaptics RMI4 to tolerate buggy firmware on some
  touchpads (e.g. ThinkPad T14 Gen 1) that report incomplete register
  descriptor structures, preventing probe failures

- A revert of an incorrect register descriptor address calculation in
  Synaptics RMI4 driver

- A fix for a regression in HP GSC PS/2 (gscps2) driver where the
  receive buffer write index was not advanced, leaving keyboard and
  mouse unusable.

Changelog:
---------

Bryam Vargas (2):
      Input: synaptics-rmi4 - bound the F3A keymap to the GPIO count
      Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count

Dmitry Torokhov (2):
      Revert "Input: rmi4 - fix register descriptor address calculation"
      Input: rmi4 - tolerate short register descriptor structure

Xu Rao (1):
      Input: gscps2 - advance receive buffer write index

Diffstat:
--------

 drivers/input/rmi4/rmi_driver.c | 39 ++++++++++++++++++++++++++-------------
 drivers/input/rmi4/rmi_f30.c    |  2 +-
 drivers/input/rmi4/rmi_f3a.c    |  2 +-
 drivers/input/serio/gscps2.c    |  1 +
 4 files changed, 29 insertions(+), 15 deletions(-)

Thanks.


-- 
Dmitry

                 reply	other threads:[~2026-06-28  5:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=akCs9sqkWvpJnCpK@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