* Tony Lindgren <tony@xxxxxxxxxxx> [120712 23:52]: > * Kevin Hilman <khilman@xxxxxx> [120712 10:55]: > > Paul Walmsley <paul@xxxxxxxxx> writes: > > > > > Commit 3dd50d0545bd5a8ad83d4339f07935cd3e883271 ("Merge tag > > > 'omap-cleanup-for-v3.6' into tmp-merge") inadvertently caused a > > > clockdomain to be registered twice on OMAP3 boards. This causes warnings > > > on boot, wild pointer dereferences, and PM regressions. Fix the double > > > registration and add some clockdomain code to prevent this from happening > > > again. As the tmp-merge branch has other branches and never goes upstream, the commit should say: Commit 472fd5401561f94698f4c8f9dbbbfbf76ab55626 (Merge branch 'cleanup-hwmod' into cleanup)... So I've updated the patch and applied it into l-o master. The patch seems to produce a new warning against arm soc tree next/cleanup branch: warning: ‘mpu_3xxx_clkdm’ defined but not used Paul, care to check if a change is needed for the arm soc tree next/cleanup branch version of this patch? Tony -- 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