On Mon, 1 Jun 2015, Tony Lindgren wrote: > * Paul Walmsley <paul@xxxxxxxxx> [150601 10:45]: > > > http://www.pwsan.com/omap/testlogs/test_v4.1-rc6/20150601012139/README.txt > > OK somehow 3517evm is listed under "skip" there? Yep that board is down right now; something's wrong with it and I haven't had the time to figure out whether it's fixable, or if it's fried. > > The best way to make this work IMHO would be for us not to accept any new > > feature addition patches as long as there are warnings reported in the > > test results. The only real exception that I would foresee is if those > > warnings are due to something outside of our control, e.g., a crappy > > bootloader, as I suspect the USB_OTG initiator warnings are for the > > CM-T3517. > > Right. Also seems we should diff dmesg output too (after stripping out > the timestamps). Pretty much the only things that should change are > the sysfs paths for devices in the dmesg output unless some warnings > get fixed. That output probably still also needs to be manually looked > at though.. Yep, there are still some other minor loose ends to be tied up too that don't show up as full warnings, such as the broken UART4 idle protocol integration on AM35xx... - Paul -- 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
