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,
Daniel Mack <zonque@gmail.com>
Subject: [git pull] Input updates for 2.6.36-rc8
Date: Mon, 18 Oct 2010 09:20:59 -0700 [thread overview]
Message-ID: <20101018162058.GA16552@core.coreip.homeip.net> (raw)
[Resending with the proper version in subject.]
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 2 important bug fixes to the evdev input handler. I hope it
is not too late to make 2.6.36...
Changelog:
---------
Daniel Mack (2):
Input: evdev - fix Ooops in EVIOCGABS/EVIOCSABS
Input: evdev - fix EVIOCSABS regression
Diffstat:
--------
drivers/input/evdev.c | 8 +++++++-
1 files changed, 7 insertions(+), 1 deletions(-)
Thanks,
Dmitry
reply other threads:[~2010-10-18 16:21 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=20101018162058.GA16552@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 \
--cc=zonque@gmail.com \
/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).