linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Uwe Bugla <uwe.bugla@gmx.de>,
	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 17:50:48 +0200	[thread overview]
Message-ID: <200705261750.48816.mb@bu3sch.de> (raw)
In-Reply-To: <200705261240.55153.uwe.bugla@gmx.de>

Andrew,

I am going to ignore Uwe from now on. It's simply impossible
to debug the problem the way he is responding.
Well, I'm not the first person in the Linux community adding
him to the killfile, ... .
I ask to try wireless-dev, as the driver works perfectly fine
for me there, but he refuses to try it, too. So I'm stuck.
I already tried your -mm kernel, but it crashes on my machine
for other reasons. (Yeah, I should look into them, too :P )

Andrew, is it possible that the breakage was introduced in the
merge process somehow? Didn't the patch apply cleanly? Are there
other changes to b44 I should know about in your tree?

If it is really impossible to debug this problem, I'd like to
suggest you to drop the b44-ssb port completely.
I'm not going to destroy my nerves any further with guys like
Uwe, so I'll include the b44-ssb port in the OpenWRT tree
and be done with it.
Although I would be very sad about it, as my longterm goal was
to make a vanilla kernel run on the OpenWRT devices... .

But maybe we can get another tester for -mm with similiar problems,
who is not bullshitting the whole time and is also going to
test wireless-dev to make sure it's not a merge bug.


-----------

And Uwe: Remember, I am not payed for this. I do _all_ this
in my free time.
So sentences like: "So, the ball has been in your court
for two days now, and you simply keep on hesitating
to take action now."
are _completely_ displaced in this discussion.

-- 
Greetings Michael.

  parent reply	other threads:[~2007-05-26 15:50 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 [this message]
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
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=200705261750.48816.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=akpm@linux-foundation.org \
    --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).