* Mike Turquette <mturquette@xxxxxxxxxx> [140117 13:00]: > Quoting Tero Kristo (2014-01-17 10:11:06) > > On 01/17/2014 07:53 PM, Tony Lindgren wrote: > > > * Kevin Hilman <khilman@xxxxxxxxxx> [140117 09:48]: > > >> Mike Turquette <mturquette@xxxxxxxxxx> writes: > > >> > > >> [...] > > >> > > >>> I took Tony's advice and fast-forwarded clk-next to -rc7 and applied > > >>> Tero's series. This includes the AM3517 bits now. I've pushed this > > >>> branch to clk-next-omap (force update) on my Linaro mirror. Can you do a > > >>> final sanity test before I merge this into clk-next? > > > > I think you accidentally merged wrong branch to clk-next-omap with the > > latest refresh. This is one is missing the build-fixes now, when it > > earlier had those in. > > > > The correct branch to merge was 3.13-rc7-dt-clks-v13-build-fixes. > > > > This also causes the build failure below for omap1. > > You are right. I broke the OMAPs. I force updated clk-next-omap (and > clk-next) with the correct branch this time. OK works for me now, thanks. 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