Re: [PATCH][v3.2.y][v3.5.y][3.8.y] Input: elantech - fix for newer hardware versions (v7)

2013-08-05 Thread Luis Henriques
Joseph Salisbury  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 
> 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 majord...@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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [PATCH][v3.2.y][v3.5.y][3.8.y] Input: elantech - fix for newer hardware versions (v7)

2013-08-05 Thread Luis Henriques
Joseph Salisbury joseph.salisb...@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 kendats...@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 majord...@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
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [PATCH][v3.2.y][v3.5.y][3.8.y] Input: elantech - fix for newer hardware versions (v7)

2013-07-19 Thread Dmitry Torokhov
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 
> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


[PATCH][v3.2.y][v3.5.y][3.8.y] Input: elantech - fix for newer hardware versions (v7)

2013-07-19 Thread Joseph Salisbury
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 
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 linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


[PATCH][v3.2.y][v3.5.y][3.8.y] Input: elantech - fix for newer hardware versions (v7)

2013-07-19 Thread Joseph Salisbury
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 kendats...@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 linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [PATCH][v3.2.y][v3.5.y][3.8.y] Input: elantech - fix for newer hardware versions (v7)

2013-07-19 Thread Dmitry Torokhov
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 kendats...@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
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/