From: JJ Ding <jj_ding@emc.com.tw>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
"Seth Forshee" <seth.forshee@canonical.com>,
"Aaron Huang" <aaron_huang@emc.com.tw>,
"Tom Lin" <tom_lin@emc.com.tw>,
"Éric Piel" <E.A.B.Piel@tudelft.nl>,
"Daniel Kurtz" <djkurtz@chromium.org>,
"Chase Douglas" <chase.douglas@canonical.com>,
"Henrik Rydberg" <rydberg@euromail.se>,
"Alessandro Rubini" <rubini@cvml.unipv.it>
Subject: Re: [PATCH v5 0/8] Input: elantech: add support for newer hardware
Date: Tue, 13 Sep 2011 09:43:30 +0800 [thread overview]
Message-ID: <874o0h43p9.fsf@emc.com.tw> (raw)
In-Reply-To: <20110909173342.GB13555@core.coreip.homeip.net>
Hi Dmitry,
On Fri, 9 Sep 2011 10:33:43 -0700, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> Hi JJ,
>
> On Mon, Sep 05, 2011 at 10:16:39AM +0800, JJ Ding wrote:
> > Hi Lists,
> >
> > This is a series of patches to add support for newer generations of ELAN
> > touchpad.
> >
> > Patches #1~#6 are essentially fixes and cleanups that pave the way for
> > patch #7 and patch #8, which really adds code for v3 and v4 hardware.
> >
> > Any comments, suggestoins are welcome.
> >
>
> OK, I applied all 8 patches to my 3.2 queue (and will push out once
> kernel.org is restored) so any followups needs to be sent relative to
> these 8.
>
> Thanks.
Happy to hear that. Thank you very much.
And thank all for reviewing and testing this series.
jj
> --
> Dmitry
> --
> 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 1:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 2:16 [PATCH v5 0/8] Input: elantech: add support for newer hardware JJ Ding
2011-09-05 2:16 ` [PATCH v5 1/8] Input: elantech - correct x, y value range for v2 hardware JJ Ding
2011-09-05 2:16 ` [PATCH v5 2/8] Input: elantech - get rid of ETP_2FT_* in elantech.h JJ Ding
2011-09-05 2:16 ` JJ Ding
2011-09-05 2:16 ` [PATCH v5 3/8] Input: elantech - use firmware provided x, y ranges JJ Ding
2011-09-05 2:16 ` JJ Ding
2011-09-05 2:16 ` [PATCH v5 4/8] Input: elantech - remove ETP_EDGE_FUZZ_V2 JJ Ding
2011-09-05 2:16 ` JJ Ding
2011-09-05 2:16 ` [PATCH v5 5/8] Input: elantech - packet checking for v2 hardware JJ Ding
2011-09-05 2:16 ` JJ Ding
2011-09-05 2:16 ` [PATCH v5 6/8] Input: elantech - clean up elantech_init JJ Ding
2011-09-05 2:16 ` JJ Ding
2011-09-05 2:16 ` [PATCH v5 7/8] Input: elantech - add v3 hardware support JJ Ding
2011-09-05 2:16 ` JJ Ding
2011-09-05 4:35 ` Daniel Kurtz
2011-09-05 4:35 ` Daniel Kurtz
2011-09-05 7:10 ` JJ Ding
2011-09-05 7:10 ` JJ Ding
2011-09-05 8:39 ` Daniel Kurtz
2011-09-05 8:47 ` Daniel Kurtz
2011-09-06 3:39 ` JJ Ding
2011-09-05 2:16 ` [PATCH v5 8/8] Input: elantech - add v4 " JJ Ding
2011-09-09 17:33 ` [PATCH v5 0/8] Input: elantech: add support for newer hardware Dmitry Torokhov
2011-09-09 17:33 ` Dmitry Torokhov
2011-09-13 1:43 ` JJ Ding [this message]
2011-09-12 8:44 ` Éric Piel
2011-09-12 8:44 ` Éric Piel
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=874o0h43p9.fsf@emc.com.tw \
--to=jj_ding@emc.com.tw \
--cc=E.A.B.Piel@tudelft.nl \
--cc=aaron_huang@emc.com.tw \
--cc=chase.douglas@canonical.com \
--cc=djkurtz@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rubini@cvml.unipv.it \
--cc=rydberg@euromail.se \
--cc=seth.forshee@canonical.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.