From: Greg KH <greg@kroah.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jouni Malinen <j@w1.fi>, Sujith <m.sujith@gmail.com>,
Sujith <Sujith.Manoharan@atheros.com>,
Senthilkumar Balasubramanian
<Senthilkumar.Balasubramanian@atheros.com>,
"John W. Linville" <linville@tuxdriver.com>,
Christoph Hellwig <hch@infradead.org>,
Vasanthakumar Thiagarajan <vasanth@atheros.com>
Subject: Re: Staging, place holder for better company/community development model
Date: Tue, 10 Mar 2009 22:00:18 -0700 [thread overview]
Message-ID: <20090311050018.GB26202@kroah.com> (raw)
In-Reply-To: <1236633633.9658.23.camel@johannes.local>
On Mon, Mar 09, 2009 at 10:20:33PM +0100, Johannes Berg wrote:
> On Mon, 2009-03-09 at 12:41 -0700, Greg KH wrote:
>
> > > Staging drivers will typically be an extremely huge amount of crap that
> > > just floods mailing lists. I don't care about those I don't read, but I
> > > would prefer to not have wireless staging drivers cross the wireless
> > > list which makes it seem like somebody is actually interested in those
> > > drivers.
> >
> > I was asked by the wireless maintainer and some of the wireless
> > developers to send such patches to the list, so that everyone knows
> > exactly what is going on in the staging tree.
>
> This is a misrepresentation, a number of people have asked for this on
> specific drivers they are actively working on and that already are in
> usable shape.
Ok, so I'll be glad to not cc: the linux-wireless list if the maintainer
asks me to.
> > That's not true, some of them are being reworked as you type, to be a
> > "real" wireless driver eventually.
> >
> > Incremental development over time is sometimes a good thing, instead of
> > total rewrites :)
>
> Except it doesn't work for most of the wireless drivers you've sucked in
> without asking any wireless developers whether that makes any sense or
> not.
Any specific examples?
thanks,
greg k-h
next prev parent reply other threads:[~2009-03-11 5:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 7:14 Staging, place holder for better company/community development model Luis R. Rodriguez
2009-03-03 7:30 ` Greg KH
2009-03-03 7:45 ` Luis R. Rodriguez
2009-03-03 15:56 ` Greg KH
2009-03-08 12:07 ` Johannes Berg
2009-03-08 22:33 ` Greg KH
2009-03-09 7:21 ` Johannes Berg
2009-03-09 19:41 ` Greg KH
2009-03-09 21:20 ` Johannes Berg
2009-03-11 5:00 ` Greg KH [this message]
2009-03-11 9:08 ` Johannes Berg
2009-03-11 16:02 ` Greg KH
2009-03-11 19:33 ` J.R. Mauro
2009-04-07 23:15 ` Greg KH
2009-03-08 23:02 ` Leon Woestenberg
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=20090311050018.GB26202@kroah.com \
--to=greg@kroah.com \
--cc=Senthilkumar.Balasubramanian@atheros.com \
--cc=Sujith.Manoharan@atheros.com \
--cc=hch@infradead.org \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=m.sujith@gmail.com \
--cc=mcgrof@gmail.com \
--cc=vasanth@atheros.com \
/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.