linux-kernel - [git pull] Input updates for 2.6.37-rc5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Wed, 15 Dec 2010 23:52:49 -0800
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-input@...r.kernel.org
Subject: [git pull] Input updates for 2.6.37-rc5

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/