From: Greg KH <gregkh@linuxfoundation.org>
To: Andreas Mohr <andi@lisas.de>
Cc: "Kristina Martšenko" <kristina.martsenko@gmail.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, devel@linuxdriverproject.org
Subject: Re: [GIT PULL] Staging driver patches for 3.17-rc1
Date: Mon, 4 Aug 2014 21:31:43 -0700 [thread overview]
Message-ID: <20140805043143.GA31519@kroah.com> (raw)
In-Reply-To: <20140805041325.GA27507@rhlx01.hs-esslingen.de>
On Tue, Aug 05, 2014 at 06:13:25AM +0200, Andreas Mohr wrote:
> > Lots of things in here, over 2000 patches, but the best part is this:
> > 1480 files changed, 39070 insertions(+), 254659 deletions(-)
> >
> > Thanks to the great work of Kristina Martšenko, 14 different staging
> > drivers have been removed from the tree as they were obsolete and no
> > one
> > was willing to work on cleaning them up.
>
> -ENOPARSE.
>
> Define "as they were obsolete and no one was willing to work on cleaning
> them up."?
>
> *Either* they're obsolete (due to better alternatives available, in the
> standard case), in which case they indeed can be removed on the spot,
> *or* they are expected to become full-service drivers and thus need cleanup.
> Which is it?
No one was willing to do the work to get these drivers out of the
staging directory. One had been broken for a number of kernel releases
with no one even noticing.
> In the case of keucr (a driver where I happen to own hardware,
> and where AFAIK this driver is required),
> I really don't see "nobody was willing to work on cleaning them up.",
> as git log tells.
Don't confuse "coding style cleanups done in a drive-by fashion" with
"willing to do the real work to get this driver merged out of the
staging tree."
> Admittedly there probably was no substantial rework,
> but it did have many janitorial changes, and some changes
> only 4 months ago even (a time frame which IMHO does not justify
> removing a driver wholesale, with the effect of certain users to not
> be able to use them then).
>
> Oh well, yet another driver where it became more difficult rather than
> easier to make forward progress.
If you are willing to do the work, I will gladly revert the patch and
look forward to patches to fix the remaining changes.
thanks,
greg k-h
next prev parent reply other threads:[~2014-08-05 4:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 19:08 [GIT PULL] Staging driver patches for 3.17-rc1 Greg KH
2014-08-05 4:13 ` Andreas Mohr
2014-08-05 4:31 ` Greg KH [this message]
2014-08-15 2:30 ` Andreas Mohr
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=20140805043143.GA31519@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=andi@lisas.de \
--cc=devel@linuxdriverproject.org \
--cc=kristina.martsenko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.