On Sun, Jul 27, 2014 at 8:30 PM, Doug Anderson <dianders@xxxxxxxxxxxx> wrote: > Kukjin, > > On Sun, Jul 27, 2014 at 5:30 PM, Kukjin Kim <kgene.kim@xxxxxxxxxxx> wrote: >> Oops, I always use my script to check kernel build like follow... >> >> $ mt >> building exynos_defconfig done >> building s3c2410_defconfig done >> building s3c6400_defconfig done >> building s5pv210_defconfig done >> >> but seems it couldn't detect the breakage from dtb :( > > Could you add a "make dtbs" in there? > > Is there any chance you could get a boot farm on this, or somehow try > to piggyback on Olof's or Kevin's boot farms (assuming they are > willing to build/boot your branch on relevant hardware)? I boot -next on the farm, and it had found the 5410 issues, which I forwarded on to some of the relevant parties (but maybe not all). I don't have any 5410 hardware so I couldn't bisect the problem and narrow it down to a single patch. Hardware currently in there is 4412 (ODROID-U3), 5250 (Arndale and Snow), 5420 and 5800 (Pit/Pi). I have a 6410-based board that I have not yet hooked up. I also boot arm-soc's for-next branch, so as soon as we merge something in I'll notice breakage, if it's somehow masked by other parts of linux-next (i.e. dependent but not described driver changes, etc). -Olof -- 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
 |