On 28 August 2013 16:01, Tomasz Figa <t.figa@xxxxxxxxxxx> wrote: > Hi Chander, > > On Wednesday 28 of August 2013 15:20:40 Chander Kashyap wrote: >> On 19 August 2013 00:57, Kukjin Kim <kgene.kim@xxxxxxxxxxx> wrote: >> > On 08/12/13 15:23, Chander Kashyap wrote: >> >> ping >> >> >> >> On 23 July 2013 15:17, Chander Kashyap<chander.kashyap@xxxxxxxxxx> > wrote: >> >>> ping. >> >>> >> >>> On 14 June 2013 20:11, Chander Kashyap<chander.kashyap@xxxxxxxxxx> >> >>> >> >>> wrote: >> >>>> Two cells were used to specify interrupts in mct node, while second >> >>>> cell >> >>>> always remains unused. Hence use only one cell. >> >>>> Suggested by Tomasz Figa. >> >>>> >> >>>> Signed-off-by: Chander Kashyap<chander.kashyap@xxxxxxxxxx> >> >>>> --- >> >>>> >> >>>> arch/arm/boot/dts/exynos4210.dtsi | 19 +++++++++---------- >> >>>> arch/arm/boot/dts/exynos4212.dtsi | 19 +++++++++---------- >> >>>> arch/arm/boot/dts/exynos4412.dtsi | 23 +++++++++++------------ >> >>>> arch/arm/boot/dts/exynos5250.dtsi | 19 +++++++++---------- >> >>>> 4 files changed, 38 insertions(+), 42 deletions(-) >> >>>> > [snip] >> > >> > Should be updated with regarding Doc. >> >> Will update the document. > > Apparently I missed your patch and did the same change for Exynos 4 SoCs in > my patch series[1] cleaning up Exynos 4 device tree files a bit. > > Since in my series it is a part of a more complex change, i.e. moving mct > node to exynos4x12.dtsi and update of MCT bindings documentation, would you > mind if we could keep with my patch doing this change for Exynos 4 and > yours taking care for Exynos 5? > > The documentation is already being updated in my series, so you could just > drop the changes done to exynos4*.dtsi files in next version. Ok, That make sense. I will post patche with changes for exynos5, only > > [1] http://thread.gmane.org/gmane.linux.kernel.samsung-soc/22207 > > Best regards, > Tomasz > -- with warm regards, Chander Kashyap -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |