All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
	Luis Henriques <luis.henriques@canonical.com>,
	Kamal Mostafa <kamal.mostafa@canonical.com>,
	rydberg@euromail.se, kendatsuba@gmail.com,
	linux-input@vger.kernel.org, stable@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Kernel Team <kernel-team@lists.ubuntu.com>
Subject: Re: [PATCH][v3.2.y][v3.5.y][3.8.y] Input: elantech - fix for newer hardware versions (v7)
Date: Fri, 19 Jul 2013 16:05:50 -0700	[thread overview]
Message-ID: <20130719230550.GA19715@core.coreip.homeip.net> (raw)
In-Reply-To: <51E9B4A1.3080205@canonical.com>

Hi Joseph,

On Fri, Jul 19, 2013 at 05:50:25PM -0400, Joseph Salisbury wrote:
> Hello,
> 
> Please consider including upstream commit
> 9eebed7de660c0b5ab129a9de4f89d20b60de68c in the next v3.2.y, v3.5.y and
> v3.8.y releases. 
> 
> It was included upstream as of v3.11-rc1.  It has been tested and
> confirmed to resolve http://bugs.launchpad.net/bugs/1166442 .
> 
> commit 9eebed7de660c0b5ab129a9de4f89d20b60de68c
> Author: Matteo Delfino <kendatsuba@gmail.com>
> Date:   Sat Jul 6 21:52:26 2013 -0700
> 
>     Input: elantech - fix for newer hardware versions (v7)
> 
> 

This fix came into my mailbox on July 06, so fairly recently. I would
prefer if we went through a few more -rcs before sending it to stable.

Thanks.

-- 
Dmitry

  reply	other threads:[~2013-07-19 23:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19 21:50 [PATCH][v3.2.y][v3.5.y][3.8.y] Input: elantech - fix for newer hardware versions (v7) Joseph Salisbury
2013-07-19 23:05 ` Dmitry Torokhov [this message]
2013-08-05 10:57 ` Luis Henriques

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=20130719230550.GA19715@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=ben@decadent.org.uk \
    --cc=joseph.salisbury@canonical.com \
    --cc=kamal.mostafa@canonical.com \
    --cc=kendatsuba@gmail.com \
    --cc=kernel-team@lists.ubuntu.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis.henriques@canonical.com \
    --cc=rydberg@euromail.se \
    --cc=stable@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.