From: "Leon Woestenberg" <leon.woestenberg@gmail.com>
To: "Greg KH" <gregkh@suse.de>
Cc: "Parag Warudkar" <parag.lkml@gmail.com>,
"Stefan Richter" <stefanr@s5r6.in-berlin.de>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
"Andreas Gruenbacher" <agruen@suse.de>,
"Jeff Mahoney" <jeffm@suse.de>
Subject: Re: [patch 00/04] RFC: Staging tree (drivers/staging)
Date: Fri, 26 Sep 2008 23:00:17 +0200 [thread overview]
Message-ID: <c384c5ea0809261400u43a3ee57y62083d20867f1cc6@mail.gmail.com> (raw)
In-Reply-To: <20080926201917.GA2591@suse.de>
Hello,
On Fri, Sep 26, 2008 at 10:19 PM, Greg KH <gregkh@suse.de> wrote:
> On Fri, Sep 26, 2008 at 04:11:49PM -0400, Parag Warudkar wrote:
>> On Fri, Sep 26, 2008 at 2:36 PM, Stefan Richter
>> <stefanr@s5r6.in-berlin.de> wrote:
>
> If you really don't like it, just never enable any of these modules,
> you'll never be bothered by it.
>
I would like new drivers for new devices to live into the wild.
Seriously, I think it's a good think to have new drivers lift along
with the kernel source distribution to get *much* wider attention,
testing, hacking and feedback.
I propose GREG_GOES_WILD and I will happily commit my
driver-in-progress to the kernel staging areas instead of to some
two-people-know-about-it-location.
Thanks for the effort, Greg,
Regards,
--
Leon
next prev parent reply other threads:[~2008-09-26 21:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080924224638.514504825@mini.kroah.org>
2008-09-24 23:00 ` Greg KH
2008-09-24 23:01 ` [patch 01/04] Staging: add TAINT_CRAP for all drivers/staging code Greg KH
2008-09-24 23:01 ` [patch 02/04] Staging: add TAINT_CRAP flag to drivers/staging modules Greg KH
2008-09-24 23:01 ` [patch 04/04] USB: add princeton instruments usb camera driver Greg KH
2008-09-24 23:01 ` [patch 03/04] Staging: add Kconfig entries and Makefile infrastructure Greg KH
2008-09-24 23:39 ` [patch 00/04] RFC: Staging tree (drivers/staging) Parag Warudkar
2008-09-25 1:03 ` Randy Dunlap
2008-09-25 2:06 ` Greg KH
2008-09-25 2:06 ` Greg KH
2008-09-25 2:59 ` Parag Warudkar
2008-09-25 4:21 ` Greg KH
2008-09-25 11:02 ` Parag Warudkar
2008-09-25 20:53 ` Greg KH
2008-09-25 21:40 ` Parag Warudkar
2008-09-25 22:04 ` Greg KH
2008-09-25 22:22 ` Parag Warudkar
2008-09-26 18:36 ` Stefan Richter
2008-09-26 20:11 ` Parag Warudkar
2008-09-26 20:19 ` Greg KH
2008-09-26 20:56 ` Parag Warudkar
2008-09-26 22:03 ` Greg KH
2008-09-26 21:00 ` Leon Woestenberg [this message]
2008-09-26 22:04 ` Greg KH
2008-09-26 20:39 ` Stefan Richter
2008-09-26 20:47 ` Parag Warudkar
2008-09-26 22:46 ` Stefan Richter
2008-09-25 5:27 ` Paul Mundt
2008-09-25 14:49 ` Randy Dunlap
2008-09-25 17:53 ` Randy Dunlap
2008-09-25 20:48 ` Greg KH
2008-09-25 21:04 ` Randy Dunlap
2008-09-25 21:51 ` Stefan Richter
2008-10-06 15:11 ` config_experimental was " Pavel Machek
2008-10-09 21:01 ` Adrian Bunk
2008-10-09 21:08 ` Greg KH
2008-10-09 21:17 ` Andrew Morton
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=c384c5ea0809261400u43a3ee57y62083d20867f1cc6@mail.gmail.com \
--to=leon.woestenberg@gmail.com \
--cc=agruen@suse.de \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=jeffm@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=parag.lkml@gmail.com \
--cc=stefanr@s5r6.in-berlin.de \
--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
all inboxes | Powered by JetHome®