* [PATCH][v3.2.y][v3.5.y][3.8.y] Input: elantech - fix for newer hardware versions (v7)
@ 2013-07-19 21:50 Joseph Salisbury
2013-07-19 23:05 ` Dmitry Torokhov
2013-08-05 10:57 ` Luis Henriques
0 siblings, 2 replies; 3+ messages in thread
From: Joseph Salisbury @ 2013-07-19 21:50 UTC (permalink / raw)
To: Ben Hutchings, Luis Henriques, Kamal Mostafa
Cc: dmitry.torokhov, rydberg, kendatsuba, linux-input, stable,
linux-kernel, Kernel Team
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
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [PATCH][v3.2.y][v3.5.y][3.8.y] Input: elantech - fix for newer hardware versions (v7)
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
1 sibling, 0 replies; 3+ messages in thread
From: Dmitry Torokhov @ 2013-07-19 23:05 UTC (permalink / raw)
To: Joseph Salisbury
Cc: Ben Hutchings, Luis Henriques, Kamal Mostafa, rydberg, kendatsuba,
linux-input, stable, linux-kernel, Kernel Team
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH][v3.2.y][v3.5.y][3.8.y] Input: elantech - fix for newer hardware versions (v7)
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
1 sibling, 0 replies; 3+ messages in thread
From: Luis Henriques @ 2013-08-05 10:57 UTC (permalink / raw)
To: Joseph Salisbury
Cc: Ben Hutchings, Kamal Mostafa, dmitry.torokhov, rydberg,
kendatsuba, linux-input, stable, linux-kernel, Kernel Team
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-08-05 10:57 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).