From: Larry Finger <larry.finger@lwfinger.net>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org, linville@tuxdriver.com,
netdev@vger.kernel.org, jgarzik@pobox.com
Subject: Re: [OOPS] bcm43xx oops on 2.6.20-rc1 on x86_64
Date: Sun, 31 Dec 2006 08:22:35 -0600 [thread overview]
Message-ID: <4597C7AB.60403@lwfinger.net> (raw)
In-Reply-To: <20061231134302.GJ20714@stusta.de>
Adrian Bunk wrote:
>
> To avoid any misunderstandings:
>
> This wasn't in any way meant against you personally.
>
> And in this case you were right, it was the same bug.
>
> My answer was based on experiences like one during 2.6.19-rc where we
> had 4 bug reports for a regression with a patch available. And it turned
> out that one of them was for a completely different regression.
>
> That's why I prefer to get confirmations that a user actually run into
> the same issue, and not into something completely different with similar
> symptoms.
I certainly understood your intent and agree that confirmation is necessary. I was venting some
frustration at it taking nearly 3 weeks to get a fix into the system for a bug that was caused by a
change in an kernel structure that was not our doing. When Andrew posted a trial patch to fix the
compilation error that resulted, I immediately responded with the two additional fixes that were
needed, but they never made it into the code. Since then I have been seeing these obscure bug
reports and quickly learned that if either softmac or bcm43xx WX were involved, this fix took care
of the problem.
Larry
next prev parent reply other threads:[~2006-12-31 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0612171510030.17532@squeaker.ratbox.org>
2006-12-30 19:21 ` [OOPS] bcm43xx oops on 2.6.20-rc1 on x86_64 Adrian Bunk
2006-12-30 21:23 ` Larry Finger
2006-12-30 21:32 ` Adrian Bunk
2006-12-30 22:45 ` Larry Finger
2006-12-31 13:43 ` Adrian Bunk
2006-12-31 14:22 ` Larry Finger [this message]
2006-12-31 4:14 ` Aaron Sethman
2006-12-31 5:14 ` Larry Finger
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=4597C7AB.60403@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bunk@stusta.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
/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).