All of lore.kernel.org
 help / color / mirror / Atom feed
From: JJ Ding <jj_ding@emc.com.tw>
To: "Éric Piel" <E.A.B.Piel@tudelft.nl>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org, Tom Lin <tom_lin@emc.com.tw>,
	Aaron Huang <aaron_huang@emc.com.tw>,
	Daniel Kurtz <djkurtz@chromium.org>
Subject: Re: [PATCH] Input: elantech - correct x, y value range for v2 hardware
Date: Wed, 17 Aug 2011 09:28:04 +0800	[thread overview]
Message-ID: <87aab86d3v.fsf@emc.com.tw> (raw)
In-Reply-To: <4E4AE637.1090000@tudelft.nl>

Hi Éric,

Thanks for the reply.

On Tue, 16 Aug 2011 23:50:47 +0200, Éric Piel <E.A.B.Piel@tudelft.nl> wrote:
> On 16-08-11 13:11, JJ Ding wrote:
> > Hi Dmitry,
> >
> > What do you think about this patch?
> > This is really a simple correction, I am wondering if it's OK to push
> > this to 3.1?
> Hi JJ Ding,
> The merge window of 3.1 is already closed, so only patches which fix 
> bugs are accepted. Is there any hardware already available for which 
> this patch solves a bug? That would be a great incentive to push it
> > :-)
As far as I know, this doesn't fix a bug. I just want to make sure the
driver and what the firmware sends are consistent.

Thank you for telling me this. I will try this again with newer hardware
support patches, aiming for 3.2 inclusion.

jj

> Éric
> 
--
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-17  1:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-15  3:51 [PATCH] Input: elantech - correct x, y value range for v2 hardware JJ Ding
2011-08-15  5:25 ` Daniel Kurtz
2011-08-15 12:45 ` Éric Piel
2011-08-16  1:12   ` JJ Ding
2011-08-16 11:11 ` JJ Ding
2011-08-16 21:50   ` Éric Piel
2011-08-17  1:28     ` JJ Ding [this message]
2011-08-17  6:43       ` Dmitry Torokhov
2011-08-17  9:53         ` Éric Piel
2011-08-17 16:37           ` Dmitry Torokhov

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=87aab86d3v.fsf@emc.com.tw \
    --to=jj_ding@emc.com.tw \
    --cc=E.A.B.Piel@tudelft.nl \
    --cc=aaron_huang@emc.com.tw \
    --cc=djkurtz@chromium.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --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.