Alexander Kochetkov <al.kochet@xxxxxxxxx> writes: > 25 нояб. 2014 г., в 22:13, Kevin Hilman <khilman@xxxxxxxxxx> написал(а): > >> I'll test your patch on all my OMAP boards. Put whatever debug output >> you want, and I'll send you links to all the boot output. > > Hello, Kevin! > > I've sent the patch[1]. Could you be so kind to run it on all your OMAP boards? > Thank you very much! > It is not urgent at all. Done. Built for omap2plus_defconfig, boot reports for all my OMAP boards here: http://people.linaro.org/~khilman/tmp/next-20141126-1-g760388ee02e4/arm-omap2plus_defconfig/ > What is the preferred way for giving patches for you (for future)? Email is fine. I have things fully automated for primary upstream trees (mainline, linux-next, stable, etc.) but for stuff like this, I can trigger one-off tests. However, if Tony wants to have a branch (besides the one already goes to linux-next) which I would add to the automation cycle, I'm willing to do that. > I have one more fixes for i2c-omap (I think final). > I don't want to break tests anymore. > > And I found, that n900 boot test PASS, but in fact it doesn't[2]. > [2] http://status.armcloud.us/boot/omap3-n900/job/next/kernel/next-20141124/defconfig/arm-omap2plus_defconfig/ Right. For these boot tests, PASS means it got to a userspace shell, which it did. The kernel got some warnings etc. during boot, but it still booted up to a shell. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
