From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: Anybody working on tidspbridge? Date: Wed, 9 Jul 2014 00:07:26 -0700 Message-ID: <20140709070726.GF28884@atomide.com> References: <53A4569B.70604@gmail.com> <53A45BBD.4040201@gmail.com> <20140629164250.GA31625@kroah.com> <53BBE895.4020105@gmail.com> <20140708143659.GB3104@kroah.com> <53BC3A94.4050208@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mho-03-ewr.mailhop.org ([204.13.248.66]:33904 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751345AbaGIHH2 (ORCPT ); Wed, 9 Jul 2014 03:07:28 -0400 Content-Disposition: inline In-Reply-To: <53BC3A94.4050208@ti.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Suman Anna Cc: Greg KH , Peter Meerwald , Kristina =?utf-8?Q?Mart=C5=A1enko?= , "devel@driverdev.osuosl.org" , "linux-omap@vger.kernel.org" , Omar Ramirez Luna * Suman Anna [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 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 I doubt anyone cares about it anymore here. > >>> > >>> Cc'ing some more people who might be interested. If no one offers to > >>> work on the driver in the next couple of days, I'll send a patch to > >>> remove it. > >> > >> I'm using the driver (with kernel 3.7) and it works reasonably well for > >> me; removing it seems a bit harsh. > > > > Using it is different from being able to maintain the code and move it > > out of the staging tree. Also, 3.7 is really old and obsolete, not much > > we can do with that kernel version :) > > > > Are you able to work on the code and do the effort needed to get it out > > of the staging tree? If so, great, if not, we are going to have to > > delete it, sorry. > > I agree with Greg here. In fact, the current TODO does not do enough > justice to the amount of work required to make it even work on the > latest kernel. Most of the TIers who worked on this driver have moved on > as Kristina would have figured with her bounced emails. So I do suggest > that this driver be deleted from the kernel tree. If there are enough > number of folks using it (not sure how many are out there), it can be > worked on out-of-tree and brought back in a cleaner fashion rather than > keeping a broken stale driver in the kernel. I agree, not much has improved with this driver since it got added into staging except just compile fixes. Regards, Tony