From: Henrik Rydberg <rydberg@euromail.se>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input: mt: Identify pointer emulation contact
Date: Fri, 10 Dec 2010 08:28:47 +0100 [thread overview]
Message-ID: <4D01D6AF.6010202@euromail.se> (raw)
In-Reply-To: <20101209234920.GA14810@core.coreip.homeip.net>
>
> So how do you propose userspace will use it? Obviously it will not help
> old dumb (ST) applications and new smart applications should understand
> MT protocol and thus do not need to pay much attention to ST events
> anyway. Apparently you have some new dumb userspace in mind here?
You are right, it is a dumb idea. Consider this one dropped.
Thanks,
Henrik
next prev parent reply other threads:[~2010-12-10 7:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 23:19 [PATCH] input: mt: Identify pointer emulation contact Henrik Rydberg
2010-12-09 23:49 ` Dmitry Torokhov
2010-12-10 7:28 ` Henrik Rydberg [this message]
2010-12-10 15:11 ` Chris Bagwell
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=4D01D6AF.6010202@euromail.se \
--to=rydberg@euromail.se \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).