[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-omap
Subject:    Tracking N770 breakage
From:       Andrew de Quincey <adq_dvb () lidskialf ! net>
Date:       2009-05-16 13:06:53
Message-ID: 20090516140653.10104565olvxrwjk () lidskialf ! net
[Download RAW message or body]

Hi, I've tracked where the N770 breaks on the linux-omap tree master branch:

This commit (REMOVE OMAP LEGACY CODE: Reset clocks and PM code to  
mainline) works fine:

http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commit;h=eba05254cb561dc27d5664503f91f7c21954e648



This next commit (Merge current mainline tree into linux-omap tree) does not:

http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commit;h=0595ee8a05836666b225e6bf003ede0da1e6e329


So "something" has been pulled back from mainline that breaks things.  
I've tried git bisecting between these two, but it seems to un-do all  
the local commits on the linux-omap tree when bisecting the merge from  
mainline, which isn't very useful.



--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[prev in list] [next in list] [prev in thread] [next in thread]