Mark Brown wrote: > > On Fri, Oct 07, 2011 at 07:56:11PM +0200, Arnd Bergmann wrote: > > On Monday 03 October 2011, Kukjin Kim wrote: > > > Mark Brown wrote: > > > > > As I reported the other day this change breaks the boot early on on the > > > > Cragganmore S3C6410 based systems (I've not actually fired up my > > > > SMDK6410 but I suspect it may have issues too). I did make some brief > > > > Hmm, I thought it has no problem when I saw Thomas Abraham's 'serial: > > > samsung' patches because he said it works fine with my for-next plus his > > > patches on SMDK6410...Anyway, I need to sort it out. > > > > Arnd, please hold this on, will request again soon. > > > Any update on this? > > We've got a lot closer to working out what's wrong (and got useful > logging) but not nailed it down yet. Kukjin has confirmed that he can > see what's likely the same issue on his systems. My suggestion is that > we go ahead with the pull request for now and then fix incrementally, > there's a relatively small set of systems affected. If it gets to more > than a couple of -rcs we know which patches are problematic and so can > always revert. Yes I agree with you and I believe we don't need to revert it during next -rc :) Arnd, could you please pull that for v3.2? If any problems, please let me know. Thanks. Best regards, Kgene. -- Kukjin Kim <kgene.kim@xxxxxxxxxxx>, Senior Engineer, SW Solution Development Team, Samsung Electronics Co., Ltd. -- 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
 |