From: Chase Douglas <chasedouglas@gmail.com>
To: JJ Ding <jj_ding@emc.com.tw>
Cc: linux-input@vger.kernel.org,
"Richard Schütz" <r.schtz@t-online.de>,
"Tom Lin" <tom_lin@emc.com.tw>,
"Aaron Huang" <aaron_huang@emc.com.tw>,
"Éric Piel" <E.A.B.Piel@tudelft.nl>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>
Subject: Re: [PATCH 0/2] Better support old elantech v2 hardware
Date: Tue, 13 Sep 2011 16:33:00 -0500 [thread overview]
Message-ID: <4E6FCC0C.3050001@gmail.com> (raw)
In-Reply-To: <1315894549-24504-1-git-send-email-jj_ding@emc.com.tw>
On 09/13/2011 01:15 AM, JJ Ding wrote:
> Hi everyone,
>
> Thanks to Richard Schütz's bug report, I did some more research on elantech
> v2 hardware. I asked our Windows driver team and firmware team about the
> _ancient histroy_ of the dark old days ;-) These two patches are the results.
>
> Hopefully with these 2 we can support v2 hardware as good as Windows does.
I just want to say: Thank you so much for all this! The Linux community
is often ignored by vendors, and then if we aren't ignored they only put
the effort into making the latest stuff work. Personally, I greatly
appreciate what you have contributed.
Thanks again!
-- Chase
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-09-13 21:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 6:15 [PATCH 0/2] Better support old elantech v2 hardware JJ Ding
2011-09-13 6:15 ` [PATCH 1/2] Input: elantech - better support all those v2 variants JJ Ding
2011-09-13 10:24 ` Richard Schütz
2011-09-13 11:28 ` JJ Ding
2011-09-13 6:15 ` [PATCH 2/2] Input: elantech - remove module parameter force_elantech JJ Ding
2011-09-13 11:02 ` [PATCH 0/2] Better support old elantech v2 hardware Éric Piel
2011-09-13 11:32 ` JJ Ding
2011-09-13 21:33 ` Chase Douglas [this message]
2011-09-14 3:43 ` JJ Ding
2011-09-14 4:32 ` M. Edward (Ed) Borasky
2011-09-16 8:56 ` JJ Ding
2011-09-16 14:21 ` Éric Piel
2011-09-19 4:54 ` JJ Ding
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=4E6FCC0C.3050001@gmail.com \
--to=chasedouglas@gmail.com \
--cc=E.A.B.Piel@tudelft.nl \
--cc=aaron_huang@emc.com.tw \
--cc=dmitry.torokhov@gmail.com \
--cc=jj_ding@emc.com.tw \
--cc=linux-input@vger.kernel.org \
--cc=r.schtz@t-online.de \
--cc=tom_lin@emc.com.tw \
/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).