public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: JJ Ding <jj_ding@emc.com.tw>
To: Seth Forshee <seth.forshee@canonical.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Alessandro Rubini <rubini@cvml.unipv.it>,
	Henrik Rydberg <rydberg@euromail.se>,
	Chase Douglas <chase.douglas@canonical.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	Aaron Huang <aaron_huang@emc.com.tw>,
	Eric Piel <E.A.B.Piel@tudelft.nl>, Tom Lin <tom_lin@emc.com.tw>,
	Daniel Kurtz <djkurtz@chromium.org>
Subject: Re: [PATCH] Input: elantech - Add v3 hardware support
Date: Thu, 18 Aug 2011 09:38:04 +0800	[thread overview]
Message-ID: <87mxf74hz7.fsf@emc.com.tw> (raw)
In-Reply-To: <20110817183544.GB31314@thinkpad-t410>

Hi Seth,

Thank you for your work.
I am preparing my patches for community review, and will submit very
soon.
Looking forward to your feedback.

Thanks.

jj

On Wed, 17 Aug 2011 13:35:44 -0500, Seth Forshee <seth.forshee@canonical.com> wrote:
> On Wed, Aug 17, 2011 at 10:31:11AM -0700, Dmitry Torokhov wrote:
> > Hi Seth,
> > 
> > On Wed, Aug 17, 2011 at 09:03:13AM -0500, Seth Forshee wrote:
> > > Adds basic v3 hardware support for newer devices not currently
> > > supported by the driver.
> > > 
> > > Thanks to Tom Lin <tom_lin@emc.com.tw> and Mark A. Stratman
> > > <stratman@gmail.com>, whose work on a previous patch revealed many
> > > of the details of the v3 protocol.
> > 
> > Excellent work, thank you.
> > 
> > Apparently Elantech is now also interested in supporting ther devices
> > on Linux and is preparing some patches adding support for the new
> > hardware so it woudl be great if we coordinated efforts. I am CC-ing
> > JJ Ding and Aaron Huang...
> 
> Sure, I'd be happy to coordinate.
> 
> Where does that leave this patch? Do you want to take it now and
> integrate improvments from working with Elantech as they come, or hold
> off? I'd personally like to see this patch get merged unless there are
> objections to it, as it works well and gives us at least some support
> for these touchpads right now. It's been tested so far on the following
> laptop models:
> 
>   Samsung NF210
>   Samsung NF310
>   Samsung QX410
>   Asus X93S
> 
> It would certainly be great to get it reviewed by the folks from
> Elantech to make sure all the details of the hardware interaction are
> correct though.
> 
> Thanks,
> Seth
> --
> 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

      reply	other threads:[~2011-08-18  1:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-17 14:03 [PATCH] Input: elantech - Add v3 hardware support Seth Forshee
2011-08-17 17:31 ` Dmitry Torokhov
2011-08-17 18:35   ` Seth Forshee
2011-08-18  1:38     ` JJ Ding [this message]

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=87mxf74hz7.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox