From mboxrd@z Thu Jan 1 00:00:00 1970 From: Larry Finger Subject: Problem with bisect Date: Sun, 05 Aug 2007 11:02:21 -0500 Message-ID: <46B5F48D.7020907@lwfinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: git@vger.kernel.org X-From: git-owner@vger.kernel.org Sun Aug 05 18:07:29 2007 Return-path: Envelope-to: gcvg-git@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1IHidd-0006lF-3Y for gcvg-git@gmane.org; Sun, 05 Aug 2007 18:07:29 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752737AbXHEQHZ (ORCPT ); Sun, 5 Aug 2007 12:07:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752589AbXHEQHZ (ORCPT ); Sun, 5 Aug 2007 12:07:25 -0400 Received: from mtiwmhc11.worldnet.att.net ([204.127.131.115]:63014 "EHLO mtiwmhc11.worldnet.att.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752073AbXHEQHY (ORCPT ); Sun, 5 Aug 2007 12:07:24 -0400 X-Greylist: delayed 302 seconds by postgrey-1.27 at vger.kernel.org; Sun, 05 Aug 2007 12:07:24 EDT Received: from [192.168.1.104] (cpe-72-129-173-253.kc.res.rr.com[72.129.173.253]) by worldnet.att.net (mtiwmhc11) with ESMTP id <20070805160221111002lquhe>; Sun, 5 Aug 2007 16:02:22 +0000 User-Agent: Thunderbird 1.5.0.12 (X11/20070509) Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: I'm helping someone find what looks like a regression in bcm43xx-mac80211 between v2.6.22 and v2.6.23-rc1. This driver is not in the mainstream kernel, but is found in John Linville's wireless-dev git tree. When we do the first bisection between the current state and v2.6.22, we obtain a kernel whose Makefile says it is v2.6.22; however, it's code is based on a state before bcm43xx-mac80211 was introduced into this tree. My memory isn't what it used to be, but I think this code was put into this tree during 2.6.19 or .20. When I used visualize to see the tree, the bottom is all the way to v2.6.16, which I think is the origin of the git process. Is this a git bug, or is it some flaw in this particular tree? We have worked around the problem by arbitrarily calling each bisection that does not have the bcm43xx-mac80211 code as "good". It has been a source of confusion for the guy I'm helping as it is his first bisection. Unfortunately, the bug doesn't show on my machine. Thanks, Larry