From: Peter Hutterer <peter.hutterer@who-t.net>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Ping Cheng <pinglinux@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] input: mt: Interface and MT_TOOL documentation updates
Date: Tue, 14 Dec 2010 13:53:05 +1000 [thread overview]
Message-ID: <20101214035303.GA11781@salty.local> (raw)
In-Reply-To: <4D0267A6.5020603@euromail.se>
On Fri, Dec 10, 2010 at 06:47:18PM +0100, Henrik Rydberg wrote:
> >>> Legacy to me implies we can upgrade, but this is hardware limitation.
>
> >>> Can we say "rectangle corner - used by older hardware"?
> >>>
> >> How about "- older hw only", to stay within a single line?
> >
> > Why do we suggest it will only be used by older hardware?
>
>
> To limit its use - we really do not want to use anything but good contact data
> anywhere, but we do not want to leave abundant (= old) hardware out, either.
> Why, is there some case where it would be useful, you think?
"old" implies a timeline but for all we know some new hardware may come out
tomorrow that requires the use of this field. so it's new old hardware then
:)
"limited capabilities hw" maybe? my bikeshed is green, btw.
Cheers,
Peter
next prev parent reply other threads:[~2010-12-14 3:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 17:24 [PATCH v2] input: mt: Interface and MT_TOOL documentation updates Henrik Rydberg
2010-12-10 17:36 ` Dmitry Torokhov
2010-12-10 17:41 ` Henrik Rydberg
2010-12-10 17:42 ` Ping Cheng
2010-12-10 17:47 ` Henrik Rydberg
2010-12-14 3:53 ` Peter Hutterer [this message]
2010-12-13 17:46 ` Chase Douglas
2010-12-13 21:21 ` Henrik Rydberg
2010-12-13 23:02 ` Chase Douglas
2010-12-13 23:25 ` Henrik Rydberg
2010-12-14 4:36 ` Peter Hutterer
2010-12-14 9:10 ` Henrik Rydberg
2010-12-20 8:17 ` Peter Hutterer
2010-12-14 14:33 ` Chris Bagwell
2010-12-14 15:02 ` 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=20101214035303.GA11781@salty.local \
--to=peter.hutterer@who-t.net \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pinglinux@gmail.com \
--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).