From: Dmitry Torokhov <dtor@insightbb.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [git pull] Input updates for 2.6.22-rc3
Date: Mon, 4 Jun 2007 01:12:52 -0400 [thread overview]
Message-ID: <200706040112.52821.dtor@insightbb.com> (raw)
Hi Linus,
Please consider pulling 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 input subsystem.
Changelog:
----------
Dmitry Torokhov (3):
Input: db9 - do not ignore dev2 module parameter
Input: ucb1x00 - do not access input_dev->private directly
Input: reduce raciness when input handlers disconnect
Uwe Bugla (1):
Input: logips2pp - fix typo in Kconfig
Diffstat:
---------
drivers/input/evdev.c | 2 +-
drivers/input/joydev.c | 2 +-
drivers/input/joystick/db9.c | 2 +-
drivers/input/mouse/Kconfig | 2 +-
drivers/input/mousedev.c | 2 +-
drivers/input/tsdev.c | 2 +-
drivers/mfd/ucb1x00-ts.c | 7 ++++---
7 files changed, 10 insertions(+), 9 deletions(-)
--
Dmitry
reply other threads:[~2007-06-04 5:13 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=200706040112.52821.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=akpm@linux-foundation.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