From: "John W. Linville" <linville@tuxdriver.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Ivo van Doorn <ivdoorn@gmail.com>, Pavel Machek <pavel@ucw.cz>,
Ingo Molnar <mingo@elte.hu>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>,
Luis Correia <luis.f.correia@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>,
Jarek Poplawski <jarkao2@gmail.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
David Miller <davem@davemloft.net>
Subject: Re: [announce] new rt2800 drivers for Ralink wireless & project tree
Date: Fri, 6 Nov 2009 13:59:50 -0500 [thread overview]
Message-ID: <20091106185950.GD2782@tuxdriver.com> (raw)
In-Reply-To: <200911061930.13069.bzolnier@gmail.com>
On Fri, Nov 06, 2009 at 07:30:13PM +0100, Bartlomiej Zolnierkiewicz wrote:
> On Friday 06 November 2009 18:58:56 Ivo van Doorn wrote:
> > the merged for those drivers after the asurance that it was only merged
> > to please the users so developers could focus on the rt2x00 version of
> > the driver.
>
> Could somebody please explain me (in the public or in the private) what is
> the reason behind whole affair about staging drivers because all the time
> I feel like I'm missing some important detail here.
I'm not 100% sure what you are asking, but I think you want to know
the basis for general objections from the people that hang-out on
linux-wireless and/or the rt2x00 team specifically?
I don't think anyone[1] has overwhelming objections to drivers in
staging for devices that have no other driver available. The main
objection is that drivers/staging steals users and (and often
developers) from the non-staging drivers, reducing the amount of
testing and development they get. In the effort to help some users,
drivers/staging effectively prolongs the amount of time those users
have to go without properly supported drivers. Much worse, none of
the wireless drivers in drivers/staging seem to have generated an
actual mergeable[2] wireless driver.
Further, the wireless drivers in drivers/staging are completely
isolated from the wireless infrastructure developments we've been
making over the past few years. The longer they live, the longer
wireless extensions will linger, the longer custom rfkill solutions
persist, and the longer we have multiple 802.11 stack implementations.
Finally, bug reports from drivers/staging are an unwelcome distraction
in bugzilla and the wireless mailing lists. Not only do those drivers
generate (often wierd) bugs, we get the privilege of looking like
jerks for refusing to deal with those reports even though we objected
to including the drivers in the first place.
It is little wonder to me why the linux-wireless folks oppose
drivers/staging...
Hth!
John
[1] Actually, I _know_ there are people who object to all of
drivers/staging, but few of those are actively and vigorously objecting
to it.
[2] A mergeable driver should respect and/or utilize existing wireless
infrastructure rather than duplicating it, as well as meeting general
standards of maintainability. Preferably it would have someone to
stand behind it as a maintainer as well.
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-11-06 18:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 18:51 [announce] new rt2800 drivers for Ralink wireless & project tree Bartlomiej Zolnierkiewicz
2009-11-03 21:00 ` Ivo van Doorn
2009-11-03 21:44 ` Bartlomiej Zolnierkiewicz
2009-11-03 22:01 ` Ivo van Doorn
2009-11-03 22:34 ` Bartlomiej Zolnierkiewicz
2009-11-03 23:09 ` Gertjan van Wingerde
2009-11-03 23:46 ` Bartlomiej Zolnierkiewicz
[not found] ` <200911040046.54247.bzolnier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-11-04 1:33 ` Julian Calaby
2009-11-04 2:28 ` Bartlomiej Zolnierkiewicz
[not found] ` <200911032334.40547.bzolnier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-11-03 23:48 ` Alan Cox
2009-11-03 23:52 ` Bartlomiej Zolnierkiewicz
2009-11-04 0:40 ` Alan Cox
2009-11-04 0:48 ` Bartlomiej Zolnierkiewicz
2009-11-04 8:37 ` Ingo Molnar
[not found] ` <20091104083737.GA16978-X9Un+BFzKDI@public.gmane.org>
2009-11-04 14:38 ` John W. Linville
2009-11-04 21:51 ` Ivo van Doorn
[not found] ` <200911042251.23506.IvDoorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-11-04 22:12 ` John W. Linville
2009-11-06 7:46 ` Pavel Machek
2009-11-06 17:58 ` Ivo van Doorn
[not found] ` <200911061858.56816.IvDoorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-11-06 18:30 ` Bartlomiej Zolnierkiewicz
2009-11-06 18:59 ` John W. Linville [this message]
2009-11-07 17:30 ` Pavel Machek
2009-11-07 18:12 ` Luis Correia
[not found] ` <efe7343f0911071012u73317883wc60f5c188bc853e8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-11-07 18:31 ` Ivo van Doorn
2009-11-07 19:43 ` Luis R. Rodriguez
[not found] ` <200911031951.05235.bzolnier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-11-03 21:01 ` Gertjan van Wingerde
2009-11-04 15:15 ` John W. Linville
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=20091106185950.GD2782@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=bzolnier@gmail.com \
--cc=davem@davemloft.net \
--cc=ivdoorn@gmail.com \
--cc=jarkao2@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luis.f.correia@gmail.com \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=penberg@cs.helsinki.fi \
--cc=rdunlap@xenotime.net \
/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).