From: Andy Ross <andy@plausible.org>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] WeTab device ID
Date: Fri, 17 Dec 2010 13:21:07 -0800 [thread overview]
Message-ID: <4D0BD443.1070803@plausible.org> (raw)
In-Reply-To: <20101217120322.GA3873@polaris>
On 12/17/2010 04:03 AM, Henrik Rydberg wrote:
> Thanks for the patch. Does the one below work for you?
Looks like this is against more recent changes than I see in the "hid"
branch of input-mt on kernel.org. I don't see a
"...EGALAX_MULTITOUCH3" defined there. Maybe you missed a push? So
not tested as-is, but certainly looks correct by inspection.
Andy
next prev parent reply other threads:[~2010-12-17 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D0AA66F.6080506@plausible.org>
2010-12-17 12:03 ` [PATCH] WeTab device ID Henrik Rydberg
2010-12-17 21:21 ` Andy Ross [this message]
2010-12-17 21:58 ` Henrik Rydberg
2010-12-17 23:03 ` Andy Ross
2010-12-18 0:06 ` Jiri Kosina
2010-12-18 6:49 ` Henrik Rydberg
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=4D0BD443.1070803@plausible.org \
--to=andy@plausible.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--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).