All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Ramiro Morales <cramm0@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Daniel Martin <consume.noise@gmail.com>,
	Filip Ayazi <filipayazi@gmail.com>,
	Linux Input <linux-input@vger.kernel.org>
Subject: Re: [PATCH] input: synaptics: min_max quirk for Thinkpad E440
Date: Wed, 25 Mar 2015 10:22:12 -0700	[thread overview]
Message-ID: <20150325172212.GB40952@dtor-ws> (raw)
In-Reply-To: <CAO7PdF_rBe1UjP3wkxhk5xh80GFFsDceGcEmWNod0zNhrQ=HkQ@mail.gmail.com>

On Wed, Mar 25, 2015 at 09:57:51AM -0300, Ramiro Morales wrote:
> On Wed, Mar 25, 2015 at 6:04 AM, Daniel Martin <consume.noise@gmail.com> wrote:
> > On 25 March 2015 at 02:20, Filip Ayazi <filipayazi@gmail.com> wrote:
> >> Sets min_max_quirk values for LEN2006 touchpad found in Lenovo Thinkpad E440
> >> (board_id=2691).
> >
> > Dmitry already applied a patch for the E440:
> >     http://www.spinics.net/lists/linux-input/msg37497.html
> 
> There are two great things about this second submission from Filip.
> 
> First, it confirms the values sent by the hardware in a second laptop
> as reported by touchpad-edge-detector.
> 
> Second, it reveals I made a stupid mistake transcribing the y_max
> value to the quirks able. The correct value is 4832 and my patch
> wrongly contains 4632.
> 
> I'm very sorry for this. I see my patch has already been pushed to the
> 'for-linus' branch and I don't know which process should we follow to
> fix the issue.

My 'for-linus' branch is stable so we need a fixup on top on the
incorrect patch, the same way as if it was already in mainline.

Thanks.

-- 
Dmitry

  reply	other threads:[~2015-03-25 17:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25  1:20 [PATCH] input: synaptics: min_max quirk for Thinkpad E440 Filip Ayazi
2015-03-25  9:04 ` Daniel Martin
2015-03-25 12:57   ` Ramiro Morales
2015-03-25 17:22     ` Dmitry Torokhov [this message]
2015-03-25 20:33       ` Filip Ayazi

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=20150325172212.GB40952@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=consume.noise@gmail.com \
    --cc=cramm0@gmail.com \
    --cc=filipayazi@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.