From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Alejandro Riveira Fernández" <ariveira@gmail.com>
Cc: Martin Steigerwald <Martin@lichtvoll.de>,
linux-kernel@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: rt2x00: slow wifi with correct basic rate bitmap (was Re: stable? quality assurance?)
Date: Tue, 13 Jul 2010 21:18:36 +0200 [thread overview]
Message-ID: <4C3CBC0C.9020003@s5r6.in-berlin.de> (raw)
In-Reply-To: <20100713200643.24ce019e@varda>
Alejandro Riveira Fernández wrote:
> El Tue, 13 Jul 2010 14:50:14 +0200
> Stefan Richter <stefanr@s5r6.in-berlin.de> escribió:
>> There were promises made in this thread? Then I must have read a
>> different mailinglist or so.
>
> Ok no promises.
> Maybe I read to much in to Mr Tso previous mail. My apologies
> [quote]
> > So I tend to use -rc3, -rc4, and -rc5 kernels on my laptops, and when
> > I find bugs, I report them and I help fix them. If more people did
> > that, then the 2.6.X.0 releases would be more stable. But kernel
> > development is a volunteer effort, so it's up to the volunteers to
> > test and fix bugs during the rc4, -rc5 and -rc6 time frame.
>
> [...]
> > [...] Linux may be a very good bargain (look
> > at how much Oracle has increased its support contracts for Solaris!),
> > but it's still not a free lunch. At the end of the day, you get what
> > you put into it.
>
> I tested the kernels i reported the bugs and helped (to the best of my
> knowledge; I'm not a programmer)
> I got no result.
"You get what you put into it" probably did not mean "report a bug, get
it fixed, every time". Often enough, kernel bugs or hardware quirks are
very hard to fix without direct access to affected hardware.
Here is how my involvement with Linux started: I reported a bug but
nobody reacted. I collected some more information, reported the bug
again, and it was immediately fixed by the driver authors. From then on
I kept following driver development as a tester and answered user
questions. A few years later, the driver authors all had left for other
projects but there were still bugs to tackle. So I started to write and
submit bug fixes myself. (I'm not a programmer either but by then I
already knew a lot about the subsystem.)
--
Stefan Richter
-=====-==-=- -=== -==-=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2010-07-13 19:19 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-11 7:18 stable? quality assurance? Martin Steigerwald
2010-07-11 8:39 ` Eric Dumazet
2010-07-11 14:22 ` Martin Steigerwald
2010-07-11 14:52 ` Martin Steigerwald
2010-07-11 15:58 ` William Pitcock
2010-07-11 16:34 ` Eric Dumazet
2010-07-16 6:59 ` Greg KH
2010-08-05 3:27 ` Jeremy Fitzhardinge
2010-07-11 17:04 ` Heinz Diehl
2010-07-11 13:16 ` Ted Ts'o
2010-07-11 18:02 ` Anca Emanuel
2010-07-12 6:46 ` David Newall
[not found] ` <AANLkTilGjfx9sb66qVfZn1SeFPURHUrrdE7JCrild8VX@mail.gmail.com>
2010-07-12 12:35 ` Fwd: " Marcin Letyns
2010-07-12 12:42 ` Alexey Dobriyan
[not found] ` <AANLkTik64lxDiCN-eRo3i_-cTqAvCzbaRI4EEXoD44Vj@mail.gmail.com>
2010-07-12 12:52 ` Fwd: " Marcin Letyns
2010-07-12 14:57 ` Valdis.Kletnieks
2010-07-12 15:56 ` David Newall
2010-07-12 17:48 ` Marcin Letyns
2010-07-12 18:00 ` Stefan Richter
2010-07-12 19:58 ` David Newall
2010-07-12 21:11 ` Stefan Richter
2010-07-12 21:39 ` Martin Steigerwald
2010-07-12 22:44 ` Stefan Richter
2010-07-15 7:23 ` david
2010-07-13 16:50 ` Theodore Tso
2010-07-13 20:45 ` David Newall
2010-07-14 6:33 ` Theodore Tso
2010-09-04 17:12 ` Martin Steigerwald
2010-07-11 13:56 ` Lee Mathers
2010-07-11 14:51 ` Martin Steigerwald
2010-07-11 17:22 ` Willy Tarreau
2010-07-11 21:38 ` Rafael J. Wysocki
2010-07-12 4:17 ` Willy Tarreau
2010-07-12 9:56 ` Martin Steigerwald
2010-07-12 15:43 ` Martin Steigerwald
2010-07-12 17:36 ` Willy Tarreau
2010-07-12 19:56 ` Martin Steigerwald
2010-07-12 23:03 ` Stefan Richter
2010-07-13 10:30 ` Martin Steigerwald
2010-07-15 7:32 ` david
2010-07-12 17:55 ` Stefan Richter
2010-09-04 16:38 ` Martin Steigerwald
2010-09-04 18:46 ` Ted Ts'o
2010-09-04 19:11 ` Martin Steigerwald
2010-09-04 23:23 ` Ted Ts'o
2010-09-05 7:59 ` Martin Steigerwald
2010-09-04 19:24 ` Stefan Richter
2010-09-04 19:34 ` Stefan Richter
2010-09-04 20:21 ` Martin Steigerwald
2010-09-04 22:50 ` Stefan Richter
2010-09-04 23:16 ` Ted Ts'o
2010-09-05 8:35 ` Avi Kivity
2010-09-05 9:48 ` Martin Steigerwald
2010-07-11 19:49 ` Stefan Richter
2010-07-13 11:11 ` Alejandro Riveira Fernández
2010-07-13 12:50 ` rt2x00: slow wifi with correct basic rate bitmap (was Re: stable? quality assurance?) Stefan Richter
2010-07-13 15:35 ` John W. Linville
2010-07-13 18:19 ` Alejandro Riveira Fernández
2010-07-13 18:38 ` John W. Linville
2010-07-13 19:07 ` Alejandro Riveira Fernández
2010-07-13 18:06 ` Alejandro Riveira Fernández
2010-07-13 19:18 ` Stefan Richter [this message]
2010-07-12 19:46 ` stable? quality assurance? Nix
[not found] ` <AANLkTimEdVsmIgXBbmhsq75ElQvGAI8avsM8-wlDpm4z@mail.gmail.com>
2010-07-15 9:09 ` Valeo de Vries
2010-07-16 7:00 ` Greg KH
2010-07-16 7:19 ` Justin P. Mattock
2010-07-16 15:25 ` Randy Dunlap
2010-07-16 15:34 ` Valeo de Vries
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=4C3CBC0C.9020003@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=Martin@lichtvoll.de \
--cc=ariveira@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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®