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: Re: [git pull] Input updates for 3.17-rc4
Date: Wed, 10 Sep 2014 14:04:14 -0700	[thread overview]
Message-ID: <20140910210414.GA24104@core.coreip.homeip.net> (raw)
In-Reply-To: <20140815061242.GA23913@core.coreip.homeip.net>

Hi Linus,

Please pull from:

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

to receive updates for the input subsystem. You will get an update to
Synaptics PS/2 driver to handle "ForcePads" (currently found in HP
EliteBook 1040 laptops), a change for Elan PS/2 driver to detect newer
touchpads, bunch of devices get annotated as Trackpoint and/or Pointer
to help userspace classify and handle them, plus assorted driver fixes.

Changelog:
---------

Dmitry Torokhov (1):
      Input: synaptics - add support for ForcePads

Hans de Goede (3):
      Input: elantech - fix detection of touchpad on ASUS s301l
      Input: add INPUT_PROP_POINTING_STICK property
      Input: add missing POINTER / DIRECT properties to a bunch of drivers

John Sung (1):
      Input: serport - add compat handling for SPIOCSTYPE ioctl

Klaus Goger (1):
      Input: cap1106 - fix register definition

Lothar Waßmann (1):
      Input: matrix_keypad - use request_any_context_irq()

Masanari Iida (1):
      Input: wm971x - fix typo in module parameter description

Nick Dyer (1):
      Input: atmel_mxt_ts - downgrade warning about empty interrupts

Stephen Warren (1):
      Input: atmel_mxt_ts - fix double free of input device


Diffstat:
--------

 drivers/input/keyboard/cap1106.c         |  4 +-
 drivers/input/keyboard/matrix_keypad.c   |  9 +++--
 drivers/input/mouse/alps.c               |  4 ++
 drivers/input/mouse/elantech.c           | 11 ++++++
 drivers/input/mouse/psmouse-base.c       |  2 +
 drivers/input/mouse/synaptics.c          | 68 ++++++++++++++++++++++++--------
 drivers/input/mouse/synaptics.h          | 11 ++++++
 drivers/input/mouse/synaptics_usb.c      |  6 +++
 drivers/input/mouse/trackpoint.c         |  3 ++
 drivers/input/serio/serport.c            | 45 +++++++++++++++++----
 drivers/input/touchscreen/atmel_mxt_ts.c | 25 +++++++++---
 drivers/input/touchscreen/wm9712.c       |  2 +-
 drivers/input/touchscreen/wm9713.c       |  2 +-
 include/uapi/linux/input.h               |  1 +
 14 files changed, 156 insertions(+), 37 deletions(-)

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-09-10 21:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15  6:12 [git pull] Input updates for 3.17-rc0 (part 2) Dmitry Torokhov
2014-09-10 21:04 ` Dmitry Torokhov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-09-10 21:08 [git pull] Input updates for 3.17-rc4 Dmitry Torokhov

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=20140910210414.GA24104@core.coreip.homeip.net \
    --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).