From: Luis Henriques <luis.henriques@canonical.com>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
Kamal Mostafa <kamal.mostafa@canonical.com>,
dmitry.torokhov@gmail.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: Mon, 05 Aug 2013 11:57:40 +0100 [thread overview]
Message-ID: <87bo5cjtgb.fsf@canonical.com> (raw)
In-Reply-To: <51E9B4A1.3080205@canonical.com> (Joseph Salisbury's message of "Fri, 19 Jul 2013 17:50:25 -0400")
Joseph Salisbury <joseph.salisbury@canonical.com> writes:
> 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)
>
>
> Sincerely,
> Joseph Salisbury
>
> --
> To unsubscribe from this list: send the line "unsubscribe stable" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Thanks, I'm queuing it for the 3.5 kernel.
Cheers,
--
Luis
prev parent reply other threads:[~2013-08-05 10:57 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
2013-08-05 10:57 ` Luis Henriques [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=87bo5cjtgb.fsf@canonical.com \
--to=luis.henriques@canonical.com \
--cc=ben@decadent.org.uk \
--cc=dmitry.torokhov@gmail.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox