linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	Luis Correia <luis.f.correia@gmail.com>,
	Mike Galbraith <efault@gmx.de>,
	linux-wireless@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [wireless] rt2870sta BUGs on shutdown, 2.6.30.2->git.today+git.wireless.today
Date: Thu, 30 Jul 2009 19:11:02 +0200	[thread overview]
Message-ID: <1248973862.22552.4.camel@johannes.local> (raw)
In-Reply-To: <200907301852.28172.IvDoorn@gmail.com>

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

On Thu, 2009-07-30 at 18:52 +0200, Ivo van Doorn wrote:

> [some text expressing his frustration]

This is exactly why I was against staging all the time. Now suddenly
"The Crap" seems like a viable alternative. WAKE UP PEOPLE. The code is
not useful. Just look at the code that Mike pasted into his email. That
alone should be enough to send cold shivers down your spine!

What staging has achieved here is giving the crap vendor code a
blessing, receiving it welcomingly and forgivingly instead of saying
"well screw you, go ahead and ship this to your users but don't ever say
you support Linux well" ... now even some hackers and just just "dumb
users" think that the crap in staging could possibly at some point
become useful code!

It won't. EVER. No matter _how_ much you clean it up, it will NEVER fit
into the code scheme that everything else wireless has adopted.

And, Bartlomiej, don't give me the straw-man argument of user support,
if all you cared about were users you could well have _distros_ ship the
crap. They don't want to, of course, support this, for good reason! As
long as the vendors don't wake up, and some people see The Crap as a
viable alternative, good hardware support will never become a reality.

Look what you've done, really! You've frustrated the only person (Ivo)
who cares about giving these devices _proper_ support to a point where
he's no longer really interested in it because he's always measured
against The Crap right away. And that's perfectly understandable!
Effectively, you're saying that while he may have done good work, you
don't care about it because it's not perfect. Mike at least was willing
to try rt2x00 and work with it.

And now you're coming out of the woods and claiming that The Crap
works?! When the thread started with how it crashed? Get real.

In the end, while the letters you typed into your email claim to say the
opposite, the message of your email is that nobody should care about
rt2x00 and that the vendor driver should remain the status quo. Well, in
that case, get lost, crawl into the staging list and at least don't
bother us with The Crap.

Such attitude is part of the problem, the other big part is that vendors
can now claim their hardware "has mainline Linux support (in the staging
area)" and nobody will be the wiser.

So how about you help work on it, or think about a solution instead?

johannes


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

  parent reply	other threads:[~2009-07-30 17:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30  9:22 [wireless] rt2870sta BUGs on shutdown, 2.6.30.2->git.today+git.wireless.today Mike Galbraith
2009-07-30  9:29 ` Johannes Berg
2009-07-30  9:44   ` Mike Galbraith
2009-07-30  9:55     ` Johannes Berg
2009-07-30 10:05       ` Mike Galbraith
2009-07-30 12:11         ` [rt2800 doesn't authenticate (wpapsk/tkip)] " Mike Galbraith
2009-08-01  5:25           ` rt2800usb: memory corruption? Mike Galbraith
2009-08-01 10:55             ` Mike Galbraith
2009-08-02  0:21               ` Pavel Roskin
2009-08-02  5:16                 ` Mike Galbraith
2009-08-02  6:29                   ` Mike Galbraith
2009-08-02  6:47                     ` Mike Galbraith
2009-08-06 10:12                       ` Pavel Roskin
2009-07-30 10:06       ` [wireless] rt2870sta BUGs on shutdown, 2.6.30.2->git.today+git.wireless.today Luis Correia
2009-07-30 13:17         ` Bartlomiej Zolnierkiewicz
2009-07-30 16:52           ` Ivo van Doorn
2009-07-30 17:09             ` Mike Galbraith
2009-07-30 17:11             ` Johannes Berg [this message]
2009-07-30 17:26               ` Greg KH
2009-07-30 18:04                 ` Dan Williams
2009-07-30 18:13                   ` Greg KH
2009-08-02  9:10         ` Peter Teoh

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=1248973862.22552.4.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=bzolnier@gmail.com \
    --cc=efault@gmx.de \
    --cc=ivdoorn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=luis.f.correia@gmail.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;
as well as URLs for NNTP newsgroup(s).