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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]