mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Greg KH <greg@kroah.com>
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: Mon, 09 Mar 2009 08:21:22 +0100	[thread overview]
Message-ID: <1236583282.4205.71.camel@johannes.local> (raw)
In-Reply-To: <20090308223304.GB11513@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]

On Sun, 2009-03-08 at 15:33 -0700, Greg KH wrote:

> > FWIW, I would MUCH prefer if the staging crap never passed any official
> > mailing lists.
> 
> What do you mean by this?  You don't ever want to see any staging
> patches on any mailing lists?  That doesn't sound helpful.

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 can provide a simple procmail rule if you really don't like this kind
> of thing, but that seems pretty extreme...

I can very well filter on my own, thank you; I'm more worried about the
noise for random third parties who then infer that this is something
that somebody is working on and that might be useful to work on for
them. Neither of that is true for any wireless staging driver, they all
require complete rewrites that can, imo, use the old code only for
reference, not for implementation.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2009-03-09  7:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03  7:14 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 [this message]
2009-03-09 19:41       ` Greg KH
2009-03-09 21:20         ` Johannes Berg
2009-03-11  5:00           ` Greg KH
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=1236583282.4205.71.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=Senthilkumar.Balasubramanian@atheros.com \
    --cc=Sujith.Manoharan@atheros.com \
    --cc=greg@kroah.com \
    --cc=hch@infradead.org \
    --cc=j@w1.fi \
    --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 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®