Hello, I found a couple of issues with todays' next (tag next-20150211) when booting an Exynos5420 Peach Pit Chromebook. These were regressions introduced when converting the clk API to return a per-user clk.
This series is composed of the following trivial fixes: Javier Martinez Canillas (2): clk: Don't dereference parent clock if is NULL clk: composite: Set clk_core to composite rate and mux components drivers/clk/clk-composite.c | 2 ++ drivers/clk/clk.c | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) Best regards, Javier -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
