Thread (26 messages) 26 messages, 6 authors, 2014-06-30

Re: [PATCH 0/4] Input: atmel_mxt_ts - make it work on Tegra

From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date: 2014-05-08 17:26:39

On Thu, May 08, 2014 at 10:41:45AM -0600, Stephen Warren wrote:
On 05/08/2014 10:01 AM, Nick Dyer wrote:
quoted
Stephen Warren wrote:
quoted
On 05/06/2014 04:16 PM, Benson Leung wrote:
quoted
Please coordinate with Nick Dyer, who has a long patch series that's
been approved but not yet merged into the input tree. The few patches
you've picked from the Chrome OS kernel overlap with his patch series.
Ah I remember you mentioning that before. Is Nick's work still active?
The link you sent me to the "latest status" was nearly a year ago:

https://lkml.org/lkml/2013/6/27/311
My latest set of patches for upstream was sent just over a month ago:
https://lkml.org/lkml/2014/3/17/403

Dmitry Torokov has signed-off on them but not merged them into his tree
yet. It would be good to hear something from him!
I don't understand the following comment in patch 0 at that link:
quoted
Hi Dimitry-

Here is a set of patches for atmel_mxt_ts that you've already
signed-off.
Surely Dmitry would only have signed off on the patches if he had
applied them somewhere. I'm puzzled why he would have applied them but
not pushed them out into linux-next.
I stashed them into a topic branch but never merged it to next because
there were concerns about the firmware loader interface causing long
pauses at startup when driver was built into the kernel. I need to go
over the series again.

Thanks.

-- 
Dmitry
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help