Hi, On Mon, 5 Feb 2018 18:37:20 +0800 Shawn Guo wrote: > On Mon, Feb 05, 2018 at 10:55:43AM +0100, Lothar Waßmann wrote: > > Hi, > > > > On Mon, 5 Feb 2018 15:56:22 +0800 Shawn Guo wrote: > > > On Fri, Jan 26, 2018 at 09:52:18AM +0100, Lothar Waßmann wrote: > > > > imx6ull-14x14-evk.dts currently includes the imx6ul.dtsi file for an > > > > i.MX6ULL SoC which is plain wrong. > > > > > > > > Rename the current imx6ul-14x14-evk.dts to .dtsi and include it from > > > > imx6ul-14x14-evk.dts and imx6ull-14x14-evk.dts, so that both can > > > > include the appropriate SoC specific (imx6ul.dtsi/imx6ull.dtsi) file. > > > > > > > > Signed-off-by: Lothar Waßmann <LW@xxxxxxxxxxxxxxxxxxx> > > > > > > Which base is the patch generated against? I cannot apply it to any > > > branch in my tree. > > > > > The patch was generated against next-20180118 but also applies to > > next-20180205. > > It looks like you would really want this go into 4.16 as a fix? In that > case, I will need to wait for v4.16-rc1 to apply it. > I don't care much when and how it will be applied. I'm not using those files myself. Lothar Waßmann -- 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
