From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input: uinput: Setup MT usage during device creation
Date: Sun, 19 Sep 2010 16:32:53 -0700 [thread overview]
Message-ID: <20100919233252.GC6565@core.coreip.homeip.net> (raw)
In-Reply-To: <1284897253-1634-1-git-send-email-rydberg@euromail.se>
On Sun, Sep 19, 2010 at 01:54:13PM +0200, Henrik Rydberg wrote:
> The input devices created by uinput do not currently handle multitouch
> properly. All events will appear as if they came from slot zero, and
> the input event buffers are not adjusted. This patch creates the MT
> slots during setup, and sets the number of events per packet based
> on the MT usage.
>
> Signed-off-by: Henrik Rydberg <rydberg@euromail.se>
Applied to 'for-linus', thank you Henrik.
--
Dmitry
prev parent reply other threads:[~2010-09-19 23:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-19 11:54 [PATCH] input: uinput: Setup MT usage during device creation Henrik Rydberg
2010-09-19 23:32 ` Dmitry Torokhov [this message]
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=20100919233252.GC6565@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rydberg@euromail.se \
/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).