From: Ingo Molnar <mingo@elte.hu>
To: kyle@infradead.org
Cc: Greg KH <gregkh@suse.de>, Dave Jones <davej@redhat.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Andrew Morton <akpm@linux-foundation.org>,
J?rn Engel <joern@logfs.org>, David Brown <lkml@davidb.org>,
Phil Oester <kernel@linuxace.com>,
Kay Sievers <kay.sievers@vrfy.org>,
Phillip Lougher <phillip@lougher.demon.co.uk>,
Christoph Hellwig <hch@infradead.org>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [GIT PULL] Squashfs pull request for 2.6.29
Date: Fri, 23 Jan 2009 00:41:45 +0100 [thread overview]
Message-ID: <20090122234145.GA469@elte.hu> (raw)
In-Reply-To: <20090122233439.GB21879@bombadil.infradead.org>
* Kyle McMartin <kyle@redhat.com> wrote:
> On Thu, Jan 22, 2009 at 03:04:57PM -0800, Greg KH wrote:
> > > Why does it need to be upstream for someone to cut their teeth helping
> > > out?
> > Because people don't know where to look if it is out-of-the tree.
> > Seriously, if it can't be easily found, it's not fixed up. Proof of
> > that is the hundreds of out-of-tree drivers that I have found over the
> > past months.
>
> What about the hundreds of utterly crap drivers we have *right now* in
> the kernel? Just because something is distributed with the kernel does
> *not* mean it will get cleaned up. There's hundreds of counterexamples
> to that. If you think moving some of them to drivers/staging to increase
> the "visibility" to people looking for low hanging fruit, I can generate
> a list...
that is true and it does not contradict the purpose and intention of
drivers/staging/ though - it extends it.
We could create drivers/staging/in/ and drivers/staging/out/.
So instead of marking drivers CONFIG_BROKEN we could move them to
drivers/staging/out/ - and if they dont get 'saved' within a kernel
release they will be zapped for good. That is more gradual than a sudden
'remove a driver completely' action.
Ingo
next prev parent reply other threads:[~2009-01-22 23:42 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 16:48 [GIT PULL] Squashfs pull request for 2.6.29 Phillip Lougher
2009-01-08 16:50 ` Christoph Hellwig
2009-01-08 17:05 ` Phillip Lougher
2009-01-08 17:11 ` Geert Uytterhoeven
2009-01-08 23:55 ` H. Peter Anvin
2009-01-09 1:53 ` Andrew Morton
2009-01-09 2:11 ` Phillip Lougher
2009-01-09 2:24 ` Kay Sievers
2009-01-09 2:36 ` Phil Oester
2009-01-09 16:54 ` Jörn Engel
2009-01-09 19:37 ` David Brown
2009-01-09 21:19 ` Jörn Engel
2009-01-10 12:43 ` Ingo Molnar
2009-01-10 16:50 ` Jörn Engel
2009-01-10 18:12 ` Andrew Morton
2009-01-10 18:30 ` Linus Torvalds
2009-01-10 19:57 ` Jeff Garzik
2009-01-10 20:16 ` Leon Woestenberg
2009-01-11 6:36 ` Valdis.Kletnieks
2009-01-10 19:19 ` Olivier Galibert
2009-01-10 22:15 ` Ingo Molnar
2009-01-11 9:30 ` Geert Uytterhoeven
2009-01-11 15:39 ` Ingo Molnar
2009-01-11 16:30 ` Greg KH
2009-01-22 21:50 ` Dave Jones
2009-01-22 21:57 ` Randy Dunlap
2009-01-22 22:15 ` Greg KH
2009-01-22 21:58 ` Greg KH
2009-01-22 22:26 ` Ingo Molnar
2009-01-22 22:50 ` Kyle McMartin
2009-01-22 23:04 ` Greg KH
2009-01-22 23:25 ` Evgeniy Polyakov
2009-01-22 23:34 ` Kyle McMartin
2009-01-22 23:41 ` Ingo Molnar [this message]
2009-01-22 23:28 ` Evgeniy Polyakov
2009-01-22 22:16 ` Ingo Molnar
2009-01-22 22:24 ` Pekka Enberg
2009-01-23 0:16 ` Andrew Morton
2009-01-23 0:30 ` Greg KH
2009-01-09 2:30 ` Harvey Harrison
2009-01-09 11:25 ` KOSAKI Motohiro
2009-01-09 12:02 ` Alan Cox
2009-01-09 21:56 ` Linus Torvalds
2009-01-09 22:08 ` Andrew Morton
2009-01-09 22:12 ` Linus Torvalds
2009-01-09 22:26 ` Alan Cox
2009-01-09 22:36 ` Harvey Harrison
2009-01-11 3:01 ` Phillip Lougher
2009-01-11 3:06 ` H. Peter Anvin
2009-01-09 16:32 ` Geert Uytterhoeven
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=20090122234145.GA469@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=joern@logfs.org \
--cc=kay.sievers@vrfy.org \
--cc=kernel@linuxace.com \
--cc=kyle@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@davidb.org \
--cc=phillip@lougher.demon.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).