I've just re-merged the build tree for the nightly builds so it's now based on v3.3, and pulled in the latest for-next from arm-soc.
I notice that the problem I reported earlier (see the "arm-soc + rmk's tree boot failure on OMAP4430SDP" thread), which results in OMAP being totally unable to boot, is still present. As far as I'm concerned, as long as this remains unfixed in arm-soc, arm-soc is not to push any branch containing the broken commit (3ec2decb) upstream. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
