All of lore.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 4.6-rc0 (round 2)
Date: Fri, 25 Mar 2016 14:02:31 -0700	[thread overview]
Message-ID: <20160325210231.GA20759@dtor-ws> (raw)

Hi Linus,

Please pull from:

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

to receive 2nd round of updates for the input subsystem. The BYD PS/2
protocol driver now uses absolute reporting mode and should behave more
like other touchpads; Synaptics driver needed to extend one of its
quirks to a newer firmware version, and a few USB drivers got tightened
up checks for the contents of their descriptors.

Changelog:
---------

Andrew Duggan (1):
      Input: synaptics-rmi4 - remove check of Non-NULL array

Benjamin Tissoires (1):
      Input: synaptics - handle spurious release of trackstick buttons, again

Oliver Neukum (2):
      Input: ims-pcu - sanity check against missing interfaces
      Input: sur40 - fix DMA on stack

Richard Pospesel (1):
      Input: byd - enable absolute mode

Sangwon Jee (1):
      Input: melfas_mip4 - add hw_version sysfs attribute

Vladis Dronov (1):
      Input: ati_remote2 - fix crashes on detecting device with invalid descriptor


Diffstat:
--------

 drivers/input/misc/ati_remote2.c        |  36 +-
 drivers/input/misc/ims-pcu.c            |   4 +
 drivers/input/mouse/byd.c               | 565 +++++++++++++++++++++-----------
 drivers/input/mouse/psmouse-base.c      |   2 +-
 drivers/input/mouse/synaptics.c         |   5 +-
 drivers/input/rmi4/rmi_driver.c         |   5 +-
 drivers/input/touchscreen/melfas_mip4.c |  28 +-
 drivers/input/touchscreen/sur40.c       |  21 +-
 8 files changed, 449 insertions(+), 217 deletions(-)


-- 
Dmitry


                 reply	other threads:[~2016-03-25 21:02 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=20160325210231.GA20759@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 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.