[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b6a2187b0903161655q15437156qc926c8db37d8ba4b@mail.gmail.com>
Date: Tue, 17 Mar 2009 07:55:49 +0800
From: Jeff Chua <jeff.chua.linux@...il.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Ingo Molnar <mingo@...e.hu>,
Johannes Berg <johannes@...solutions.net>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Adrian Bunk <bunk@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
Network Development <netdev@...r.kernel.org>,
"John W. Linville" <linville@...driver.com>
Subject: Re: 2.6.29-rc8: Reported regressions from 2.6.28
On Tue, Mar 17, 2009 at 3:57 AM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> IOW, if you've pinpointed 71c11fb57b924c160297ccd9e1761db598d00ac2 as
> being bad, then you should go back and double-check that its parent
> (in this case 4607816f608b42a5379aca97ceed08378804c99f) is good.
> Because if it's parent is also bad, then that just means that you made
> some mistake in "git bisect".
> In this case, it really sounds like maybe you marked the parent good, even
> though you should have marked it bad.
I should have been more careful, just got thrown off during the last
few steps of the bisect. But with the bad association to the AP after
a57a59f247b651e8ed6d3eeb7e2f9d83b83134c9 (iwlwifi: remove implicit
direct scan), can someone suggest where to go from here?
Meanwhile, I'll try bisecting again.
Thanks,
Jeff.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists