From: rydberg@euromail.se
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: [GIT PULL] input: mt updates for 3.11
Date: Thu, 27 Jun 2013 14:40:11 +0000 [thread overview]
Message-ID: <20130627144011.GA553@polaris.bitmath.org> (raw)
Hi Dmitry,
Please pull the for-next branch to receive a trivial MT documentation fix.
Thanks,
Henrik
The following changes since commit 317ddd256b9c24b0d78fa8018f80f1e495481a10:
Linux 3.10-rc5 (2013-06-08 17:41:04 -0700)
are available in the git repository at:
git://github.com/rydberg/linux.git for-next
for you to fetch changes up to 257867dc8d893690c175c1f717f91c3b6d44a63d:
Input: MT - Specify that ABS_MT_SLOT must have a minimum of 0 (2013-06-13 21:32:00 +0200)
----------------------------------------------------------------
Peter Hutterer (1):
Input: MT - Specify that ABS_MT_SLOT must have a minimum of 0
Documentation/input/multi-touch-protocol.txt | 2 ++
1 file changed, 2 insertions(+)
reply other threads:[~2013-06-27 15:03 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=20130627144011.GA553@polaris.bitmath.org \
--to=rydberg@euromail.se \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.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).