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: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: [git pull] Input updates for 2.6.37-rc5
Date: Wed, 15 Dec 2010 23:52:49 -0800	[thread overview]
Message-ID: <20101216075249.GC26567@core.coreip.homeip.net> (raw)

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.

The main change it that we define new versions of EVIOC{G|S}KEYCODE_V2
ioctls instead of reusing the old names. This is to avoid surprising
people recompiling programs using old interface on newer kernels (while
we kept ABI intact so existing binaries should continue working fine
recompiled programs would start failing since they'd be using old ioctl
data with new ioctl numbers).

Changelog:
---------

Dmitry Torokhov (1):
      Input: define separate EVIOCGKEYCODE_V2/EVIOCSKEYCODE_V2

Kevin Granade (1):
      Input: wacom - add another Bamboo Pen ID (0xd4)


Diffstat:
--------

 drivers/input/evdev.c            |  113 +++++++++++++++++++------------------
 drivers/input/tablet/wacom_wac.c |    3 +
 include/linux/input.h            |    6 +-
 3 files changed, 65 insertions(+), 57 deletions(-)

-- 
Dmitry


             reply	other threads:[~2010-12-16  8:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-16  7:52 Dmitry Torokhov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-12-08  5:33 [git pull] Input updates for 2.6.37-rc5 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=20101216075249.GC26567@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --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).