From: Michael Buesch <mb@bu3sch.de>
To: Uwe Bugla <uwe.bugla@gmx.de>
Cc: Larry Finger <larry.finger@lwfinger.net>,
Andrew Morton <akpm@linux-foundation.org>,
Maximilian Engelhardt <maxi@daemonizer.de>,
linux-wireless@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400)
Date: Sat, 26 May 2007 23:58:29 +0200 [thread overview]
Message-ID: <200705262358.30038.mb@bu3sch.de> (raw)
In-Reply-To: <200705262332.50640.uwe.bugla@gmx.de>
On Saturday 26 May 2007 23:32:50 Uwe Bugla wrote:
> Hint: Although being a "non-hacker" or "non-developer" I do have stepped
...
> In so far, if you continue to state that debugging is nothing but guessing
> around wildly you are definitely wrong, showing us all your missing code
> hacker experience. If you DO continue like this every step will be a torture
> not only for me but for the reading folks as well.
You REALLY want to tell me, a developer and maintainer of several
big projects, how debugging is done, being a non-developer and non-hacker?
I can't believe what I am reading here.
> The fact that you simply ignored to imply those functions and continue to call
> other people dumb shows exactly how small and humble you are.
Please quote me where I called someone dumb.
Ah, yes. I am inhuman and whatever. We know that already.
> Apart from that:
> The message that you rooted to my place was no "proof" at all for any kind of
> disfunctionality or compatibility issue!
>
> In that message the lack of performance of the "enclosed" or "old"
> or "complete" b44 module (i. e. PCI-only module) was criticised, NOT the one
> ripped by you personally into two modules called b44 and ssb.
Ah, no? I think you didn't completely understand the mail.
Steve reported a bug in b44 2.6.22. Please note that 2.6.22 does NOT include
ssb. But I'm sure you'll find a way to make me responsible for
this bug, anyway.
b44 is buggy and this is NOT caused by ssb. Re-read steve's mail.
> In so far I would deeply appreciate you personally to stick to the facts in
> your personal lack of knowledge about the b44 driver instead of playing bad
> politics against other people like me and others.
Oh, poor poor guy.
I lack knowledge about b44? Oh, I suppose that was a typo and you
meant yourself.
> Hello my dear Andrew Morton,
>
> Could you please do me and the rest of the world two favours?
>
> A. Rip Michael Buesches code out of the mm-tree
>
> B. Give Michael Buesch a fair chance to revise his disfunctionable code
> outside the mm-tree and / or the vanilla mainline.
Andrew, I see that you are in a bad situation now.
I respect every decision you make. But please still
consider that b44 works perfectly well for me. I tested it
today on _all_ kernels that did not work for Uwe in this thread.
On my device (BCM4401-B0) it works on all of these kernels.
I'd suggest we leave the code in the -mm tree and wait for
someone else to show up with a bugreport.
It's simply impossible to debug this problem with the help of Uwe.
> C: calling all people simply dumb who do not know about his personal issues at
> all
Please quote this, Uwe.
> Thank you, Andrew Morton! You are real fine!
>
> Sincerely
>
> Uwe
>
>
Uwe, I just added you to my killfile.
Don't bother sending mail to me any longer. It will not arrive.
I'm not interested in your stupid "bugreports" anymore, as they are
useless and consist only of personal insults and
personal miscreditations.
Welcome to the killfile of yet another kernel developer.
--
Greetings Michael.
next prev parent reply other threads:[~2007-05-26 21:58 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070524195616.234280@gmx.net>
2007-05-24 20:06 ` BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400) Andrew Morton
2007-05-24 21:16 ` Uwe Bugla
2007-05-25 13:16 ` Michael Buesch
2007-05-25 13:12 ` Michael Buesch
2007-05-25 13:20 ` Michael Buesch
2007-05-25 13:59 ` Uwe Bugla
2007-05-25 14:52 ` Michael Buesch
2007-05-25 15:59 ` Uwe Bugla
2007-05-25 16:23 ` Michael Buesch
2007-05-25 18:48 ` Maximilian Engelhardt
2007-05-25 19:40 ` Uwe Bugla
2007-05-26 5:00 ` Michael Buesch
2007-05-26 9:39 ` Maximilian Engelhardt
2007-05-26 10:40 ` Uwe Bugla
2007-05-26 15:36 ` Michael Buesch
2007-05-26 15:52 ` Uwe Bugla
2007-05-26 15:50 ` Michael Buesch
2007-05-26 16:13 ` Andrew Morton
2007-05-26 16:20 ` Uwe Bugla
2007-05-26 16:46 ` Francois Romieu
2007-05-26 16:21 ` Michael Buesch
2007-05-26 16:26 ` Uwe Bugla
2007-05-26 16:40 ` Michael Buesch
2007-05-26 17:04 ` Uwe Bugla
2007-05-26 17:18 ` Michael Buesch
2007-05-26 17:24 ` Uwe Bugla
2007-05-26 18:03 ` Michael Buesch
2007-05-26 18:19 ` Andrew Morton
2007-05-26 19:38 ` Uwe Bugla
2007-05-26 19:57 ` Larry Finger
2007-05-26 20:22 ` Francois Romieu
2007-05-26 20:33 ` Uwe Bugla
2007-05-26 21:00 ` Michael Buesch
2007-05-26 18:41 ` Benoit Boissinot
2007-05-26 18:46 ` Michael Buesch
2007-05-26 18:58 ` Uwe Bugla
2007-05-26 19:14 ` Michael Buesch
2007-05-26 19:19 ` Michael Buesch
2007-05-26 19:39 ` Uwe Bugla
2007-05-26 19:49 ` Michael Buesch
2007-05-26 21:32 ` Uwe Bugla
2007-05-26 21:52 ` Dan Williams
2007-05-26 22:16 ` Uwe Bugla
2007-05-26 21:58 ` Michael Buesch [this message]
2007-05-26 19:04 ` Michael Buesch
2007-05-28 12:12 ` Michael Buesch
2007-05-26 16:14 ` Uwe Bugla
2007-05-26 22:42 ` David Miller
2007-05-25 16:56 ` Andrew Morton
2007-05-25 18:42 ` Uwe Bugla
2007-05-27 10:46 Uwe Bugla
2007-05-27 13:41 ` Kyle Moffett
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=200705262358.30038.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=akpm@linux-foundation.org \
--cc=larry.finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=maxi@daemonizer.de \
--cc=uwe.bugla@gmx.de \
/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).