On Thu, Jul 10, 2014 at 08:54:18AM +0300, Ivaylo Dimitrov wrote:
On 9.07.2014 10:07, Tony Lindgren wrote:
* Suman Anna s-a...@ti.com [140708 11:40]:
Hi Peter,
On 07/08/2014 09:36 AM, Greg KH wrote:
On Tue, Jul 08, 2014 at 03:03:58PM +0200, Peter Meerwald wrote:
Hello,
Given the
On Thu, Jul 10, 2014 at 12:11 PM, Greg KH gre...@linuxfoundation.org wrote:
On Thu, Jul 10, 2014 at 08:54:18AM +0300, Ivaylo Dimitrov wrote:
On 9.07.2014 10:07, Tony Lindgren wrote:
* Suman Anna s-a...@ti.com [140708 11:40]:
Hi Peter,
On 07/08/2014 09:36 AM, Greg KH wrote:
On
* Suman Anna s-a...@ti.com [140708 11:40]:
Hi Peter,
On 07/08/2014 09:36 AM, Greg KH wrote:
On Tue, Jul 08, 2014 at 03:03:58PM +0200, Peter Meerwald wrote:
Hello,
Given the total lack of response here, I suggest just deleting the
driver. No one has ever done the real work that is
On 9.07.2014 10:07, Tony Lindgren wrote:
* Suman Anna s-a...@ti.com [140708 11:40]:
Hi Peter,
On 07/08/2014 09:36 AM, Greg KH wrote:
On Tue, Jul 08, 2014 at 03:03:58PM +0200, Peter Meerwald wrote:
Hello,
Given the total lack of response here, I suggest just deleting the
driver. No one
On 29/06/14 19:42, Greg KH wrote:
On Fri, Jun 20, 2014 at 07:05:17PM +0300, Kristina Martšenko wrote:
On 20/06/14 18:43, Kristina Martšenko wrote:
Hi Omar,
I'm helping Greg do a bit of cleanup in the staging tree. I noticed that
nobody seems to have worked towards moving tidspbridge out of
Hello,
Given the total lack of response here, I suggest just deleting the
driver. No one has ever done the real work that is going to be
required to get this code out of staging. It has had build errors
causing it to not even be usable for some kernel versions with no one
noticing, so
On Tue, Jul 08, 2014 at 03:03:58PM +0200, Peter Meerwald wrote:
Hello,
Given the total lack of response here, I suggest just deleting the
driver. No one has ever done the real work that is going to be
required to get this code out of staging. It has had build errors
causing it to
Hi Peter,
On 07/08/2014 09:36 AM, Greg KH wrote:
On Tue, Jul 08, 2014 at 03:03:58PM +0200, Peter Meerwald wrote:
Hello,
Given the total lack of response here, I suggest just deleting the
driver. No one has ever done the real work that is going to be
required to get this code out of
