On Thu, Dec 13, 2012 at 12:59:49, Paul Walmsley wrote: > On Thu, 13 Dec 2012, Hiremath, Vaibhav wrote: > > > On Thu, Dec 13, 2012 at 11:11:49, Paul Walmsley wrote: > > > > > > The branch name to use is: > > > > > > "TEST_pwrdm_post_fpwrst_devel_a_3.9" > > > > If I am correct, it only includes one additional patch (merge commit), > > right??? > > > > commit d94831e0005fee743cefd28f4c20b7c435c71236 > > Merge: 3e885c6 80ab3b2 > > Author: Paul Walmsley <paul@xxxxxxxxx> > > Date: Sun Dec 9 13:06:51 2012 -0700 > > > > build fixes > > > > > > > > Does this also fix sparse warnings? > > Just ran a quick sparse check on mach-omap2 at 3e885c6 and d94831e with > 'make -j4 C=2 arch/arm/mach-omap2', and no warnings showed up. There were > some sparse issues that got fixed at an earlier point, though, so perhaps > you have an older copy of the branches somehow? > Ignore my earlier comment on sparse warning, it was my wrong sparse tool which was culprit here. I am working on remote server, which has sparse present inside /usr/bin, and somehow my default config using that one instead of what I was building. I fixed this by changing the PATH, and now I do not see any issues/warnings. Thanks, Vaibhav -- 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
