Tracking N770 breakage

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux