Re: OMAP2430 build breakage and git bisect issues

[Tony Lindgren <tony@atomide.com>]

* Gadiyar, Anand <gadiyar@ti.com> [080408 14:20]:
> Hi all,
> 
> omap_2430sdp_defconfig and omap_2430osk_defconfig builds seem to be broken. (also reported at [1])
> 
> I tried to use git bisect to narrow down the exact patch that caused this and it looks like some patches that got merged don't compile individually. This causes the git bisect process to fail.
> 
> For instance, this happens when git bisect lands me in the middle of a mainline merge. Then I can't do a make omap_*_defconfig.
> 
> In other cases than a mainline merge, some patches are not individually compilable.
> For instance commit [2b2d5f705f1f5fad4275401d695697c06ad1e886] ARM: OMAP: More fixes for cm and prm assembly access
> 
> How do I recover from this? Or move to a compilable patch near to the bisect point?

You can mark mark the next commit with git-bisect bad and then continue.

But in general, we should have compiling and booting commits. While
doing merge things can break if the commit is created automatically.

I'll try to remember to test build the merge before commit next time :)

Tony



> [1] http://opensource.indt.org/omapbuilds/