On Thu, Aug 3, 2017 at 8:02 PM, Ulf Hansson <ulf.hansson@xxxxxxxxxx> wrote: > On 3 August 2017 at 13:25, Chen-Yu Tsai <wens@xxxxxxxx> wrote: >> On Thu, Aug 3, 2017 at 7:19 PM, Ulf Hansson <ulf.hansson@xxxxxxxxxx> wrote: >>> On 26 July 2017 at 21:45, Maxime Ripard >>> <maxime.ripard@xxxxxxxxxxxxxxxxxx> wrote: >>>> On Wed, Jul 26, 2017 at 10:09:41PM +0800, Chen-Yu Tsai wrote: >>>>> On Mon, Jul 24, 2017 at 9:58 PM, Chen-Yu Tsai <wens@xxxxxxxx> wrote: >>>>> > Hi everyone, >>>>> > >>>>> > This is v3 of my MMC controller support series. >>>>> > >>>>> >>>>> [...] >>>>> >>>>> > Chen-Yu Tsai (10): >>>>> > clk: sunxi-ng: Add interface to query or configure MMC timing modes. >>>>> > clk: sunxi-ng: Add MP_MMC clocks that support MMC timing modes >>>>> > switching >>>>> > clk: sunxi-ng: a83t: Support new timing mode for mmc2 clock >>>>> > mmc: sunxi: Support controllers that can use both old and new timings >>>>> > mmc: sunxi: Support MMC DDR52 transfer mode with new timing mode >>>>> > mmc: sunxi: Add support for A83T eMMC (MMC2) >>>>> >>>>> So this series seems to be ready for inclusion, unless Ulf has further >>>>> concerns about the clk usage. >>>>> >>>>> The first mmc patch have build time dependencies on the first clk patch. >>>>> Shall we put the clk patch on a separate immutable branch for both trees >>>>> to pull? Or we could just merge everything through the mmc tree? I don't >>>>> think we'll touch this part of the sunxi-ng clk driver for the remainder >>>>> of this cycle. >>>> >>>> I guess the easiest would be for it to go through Ulf tree, unless he >>>> says otherwise of course :) >>> >>> Okay, I have picked up the series and applied it for my next branch. >> >> I guess I wasn't very clear. When I meant "everything" I meant the mmc >> and clk patches. We will take the dts patches through the sunxi tree. >> >> Can you drop the four dts patches from your tree? That would be the >> last four patches on mmc/next at the moment. > > Done! Thanks! I applied the remaining dts patches to the sunxi tree. ChenYu -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
