On 27/10/15 14:08, Stephen Boyd wrote: > On 10/26, Florian Fainelli wrote: >> Hi all, >> >> This patch series adds support for the Broadcom BCM63138 DSL SoCs >> clocking framework. >> >> Since the HW is identical to the one found in Broadcom iProc SoCs, but the >> integration is different (obviously), there is still a new compatible string >> introduced just in case we happen to find issues in the future. >> >> This applies on top of clk/next as of >> 679c51cffc3b316bd89ecc91ef92603dd6d4fc68 ("clk: Add stubs for of_clk_*() >> APIs when CONFIG_OF=n") >> >> Since there is an obvious dependency between patch 2 and 3, we can either >> merge this through the Clock tree or via a future arm-soc pull requests >> for Broadcom SoCs. > > One way to avoid the dependency would be to stage the first two > patches in clk tree under clk-bcm63xxx and then pull that into > your local branch via git FETCH && git checkout FETCH_HEAD and > then apply the 3rd patch on top, tag it and send it off to > arm-soc. This way, when arm-soc merges into linus' tree the > dependency is taken care of and we don't take anything for dtsi > files through the clk tree. It looks like nothing bad will happen > if patch 2 is merged before patch 3.
Works for me, thanks! -- Florian -- To unsubscribe from this list: send the line "unsubscribe linux-clk" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html