Search Linux Wireless

Re: Biescting between mainline and wireless-testing

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 05/06/2011 07:34 PM, Ben Greear wrote:
On 05/06/2011 04:51 PM, RafaÅ MiÅecki wrote:
I suspect we have some ugly (hard trackable) regression between
mainline and wireless-testing. It sounds impossible, but this seems to
affect Broadcom cards and looks like not related to ssb or b43.

Today I've compiled 2.6.38 and 2.6.39-rc6, both work GOOD.
I've compiled wireless-testing and it failed, BAD.
I've reverted all recent ssb patches from top and it still fails BAD.

What would be the easiest way to try bisecting? I can see
wireless-testing merges mainline quite often. Can I use some trick on
checkouted wireless-testing? Do I have to checkout mainline and merge
wireless-testing into it? Something even different?


git bisect can handle it...I've spent some quality time finding
bugs in ath9k with that lately...

The other thing to do is to see if branching wire-testing to 2.6.38 results in a workable system.

What card fails? I've been busy with Realtek hardware lately and have not run very much with Broadcom, but my 4311 worked earlier this week.

Larry
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux