From: Larry Finger <Larry.Finger@lwfinger.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
linux-wireless@vger.kernel.org,
b43-dev <b43-dev@lists.infradead.org>
Subject: Re: Biescting between mainline and wireless-testing
Date: Fri, 06 May 2011 20:13:49 -0500 [thread overview]
Message-ID: <4DC49CCD.7040906@lwfinger.net> (raw)
In-Reply-To: <4DC49386.6070503@candelatech.com>
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
next prev parent reply other threads:[~2011-05-07 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 23:51 Biescting between mainline and wireless-testing Rafał Miłecki
2011-05-07 0:34 ` Ben Greear
2011-05-07 1:13 ` Larry Finger [this message]
2011-05-07 8:24 ` Rafał Miłecki
2011-05-07 8:20 ` Rafał Miłecki
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=4DC49CCD.7040906@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.com \
/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).