git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Problem with bisect

From
LFLarry Finger <larry.finger@lwfinger.net>
Date
Aug 5, 2007, 16:02 UTC
Message-ID
<46B5F48D.7020907@lwfinger.net>

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
Next: Christian Couder
Message 1 of 9 in “Problem with bisect”
  1. Larry FingerAug 5, 2007
  2. Christian CouderAug 7, 2007
  3. Larry FingerAug 7, 2007
  4. Christian CouderAug 7, 2007
  5. Larry FingerAug 5, 2007
  6. Thomas GlanzmannAug 5, 2007
  7. Larry FingerAug 5, 2007
  8. SeanAug 6, 2007
  9. Larry FingerAug 6, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.