Hi Shawn, How do you suggest to fix this issue? Can we cook a patch for it directly based on linux-next tree? Regards Dong Aisheng On Mon, Jan 6, 2014 at 2:22 PM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > Hi all, > > On Tue, 17 Dec 2013 16:06:19 +0800 Dong Aisheng <dongas86@xxxxxxxxx> wrote: >> >> I tested that Chris tree does not have problem. >> It's caused by IMX tree updates. >> >> Chris, >> Is the way Shawn suggested OK for you? > > Can we have some resolution of this please? This failed to build again > today so I have used the version of the mmc tree from next-20131212 > again. I tried the obvious fix (s/pinctrl_usdhc4_1/pinctrl_usdhc4/) but > that didn't work. > > -- > Cheers, > Stephen Rothwell sfr@xxxxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
