linux-input.vger.kernel.org archive mirror
 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 v5.7-rc7
Date: Wed, 27 May 2020 21:43:43 -0700	[thread overview]
Message-ID: <20200528044343.GA109749@dtor-ws> (raw)

Hi Linus,

Please pull from:

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

to receive updates for the input subsystem. Just a few random driver
fixups.

Changelog:
---------

Brendan Shanks (1):
      Input: evdev - call input_flush_device() on release(), not flush()

Christophe JAILLET (1):
      Input: dlink-dir685-touchkeys - fix a typo in driver name

Dennis Kadioglu (1):
      Input: synaptics - add a second working PNP_ID for Lenovo T470s

Dmitry Torokhov (1):
      Revert "Input: i8042 - add ThinkPad S230u to i8042 nomux list"

Enric Balletbo i Serra (1):
      Input: cros_ec_keyb - use cros_ec_cmd_xfer_status helper

Evan Green (1):
      Input: synaptics-rmi4 - really fix attn_data use-after-free

Gustavo A. R. Silva (1):
      Input: applespi - replace zero-length array with flexible-array

Hans de Goede (1):
      Input: axp20x-pek - always register interrupt handlers

James Hilliard (1):
      Input: usbtouchscreen - add support for BonXeon TP

Johnny Chuang (1):
      Input: elants_i2c - support palm detection

Kevin Locke (2):
      Input: i8042 - add ThinkPad S230u to i8042 nomux list
      Input: i8042 - add ThinkPad S230u to i8042 reset list

Stephan Gerhold (1):
      Input: mms114 - fix handling of mms345l

Wei Yongjun (1):
      Input: synaptics-rmi4 - fix error return code in rmi_driver_probe()

Wolfram Sang (1):
      Input: lm8333 - update contact email

Łukasz Patron (1):
      Input: xpad - add custom init packet for Xbox One S controllers

Diffstat:
--------

 drivers/input/evdev.c                           | 19 ++-----
 drivers/input/joystick/xpad.c                   | 12 +++++
 drivers/input/keyboard/applespi.c               |  2 +-
 drivers/input/keyboard/cros_ec_keyb.c           | 14 ++---
 drivers/input/keyboard/dlink-dir685-touchkeys.c |  2 +-
 drivers/input/misc/axp20x-pek.c                 | 72 +++++++++++++------------
 drivers/input/mouse/synaptics.c                 |  1 +
 drivers/input/rmi4/rmi_driver.c                 |  5 +-
 drivers/input/serio/i8042-x86ia64io.h           |  7 +++
 drivers/input/touchscreen/elants_i2c.c          | 11 +++-
 drivers/input/touchscreen/mms114.c              | 12 ++---
 drivers/input/touchscreen/usbtouchscreen.c      |  1 +
 include/linux/input/lm8333.h                    |  2 +-
 13 files changed, 88 insertions(+), 72 deletions(-)

Thanks.


-- 
Dmitry

             reply	other threads:[~2020-05-28  4:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28  4:43 Dmitry Torokhov [this message]
2020-05-28 21:10 ` [git pull] Input updates for v5.7-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=20200528044343.GA109749@dtor-ws \
    --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;
as well as URLs for NNTP newsgroup(s).