From: Greg KH <gregkh@linuxfoundation.org>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: devel@driverdev.osuosl.org, linux-omap@vger.kernel.org
Subject: Re: Anybody working on tidspbridge?
Date: Tue, 8 Jul 2014 07:36:59 -0700 [thread overview]
Message-ID: <20140708143659.GB3104@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.01.1407081452580.5181@pmeerw.net>
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.
greg k-h
next prev parent reply other threads:[~2014-07-08 14:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53A4569B.70604@gmail.com>
[not found] ` <53A45BBD.4040201@gmail.com>
[not found] ` <20140629164250.GA31625@kroah.com>
2014-07-08 12:48 ` Anybody working on tidspbridge? Kristina Martšenko
2014-07-08 13:03 ` Peter Meerwald
2014-07-08 14:36 ` Greg KH [this message]
2014-07-08 18:38 ` Suman Anna
2014-07-09 7:07 ` Tony Lindgren
2014-07-10 5:54 ` Ivaylo Dimitrov
2014-07-10 16:11 ` Greg KH
2014-07-10 16:18 ` Jason Kridner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140708143659.GB3104@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-omap@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox