Hi Hans, All the dependences of this patch have been merged into v4.10-next.Could you take v9 of this patch set? Matthias will help us to take the dts part. Best Regards, Rick On Fri, 2017-01-13 at 16:02 +0100, Matthias Brugger wrote: > Hi James, > > On 10/01/17 02:28, Eddie Huang wrote: > > Hi Matthias, > > > > On Mon, 2017-01-09 at 19:45 +0100, Matthias Brugger wrote: > >> > >> On 09/01/17 12:29, Hans Verkuil wrote: > >>> Hi Rick, > >>> > >>> On 01/06/2017 03:34 AM, Rick Chang wrote: > >>>> Hi Hans, > >>>> > >>>> The dependence on [1] has been merged in 4.10, but [2] has not.Do you have > >>>> any idea about this patch series? Should we wait for [2] or we could merge > >>>> the source code and dt-binding first? > >>> > >>> Looking at [2] I noticed that the last comment was July 4th. What is the reason > >>> it hasn't been merged yet? > >>> > >>> If I know [2] will be merged for 4.11, then I am fine with merging this media > >>> patch series. The dependency of this patch on [2] is something Mauro can handle. > >>> > >>> If [2] is not merged for 4.11, then I think it is better to wait until it is > >>> merged. > >>> > >> > >> I can't take [2] because there is no scpsys in the dts present. It seems > >> that it got never posted. > >> > >> Rick can you please follow-up with James and provide a patch which adds > >> a scpsys node to the mt2701.dtsi? > >> > > > > James sent three MT2701 dts patches [1] two weeks ago, these three > > patches include scpsys node. Please take a reference. And We will send > > new MT2701 ionmmu/smi dtsi node patch base on [1] later, thus you can > > accept and merge to 4.11. > > > > Thanks for the clarification. I pulled all this patches into > v4.10-next/dts32 > > Hans will you take v9 of this patch set? > Then I'll take the dts patch. > > Regards, > Matthias > > > [1] > > https://patchwork.kernel.org/patch/9489991/ > > https://patchwork.kernel.org/patch/9489985/ > > https://patchwork.kernel.org/patch/9489989/ > > > > Thanks, > > Eddie > > > > -- 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
