On Mon, May 6, 2013 at 1:14 PM, Stephen Warren <swarren@xxxxxxxxxxxxx> wrote: > On 05/06/2013 01:54 PM, Russell King - ARM Linux wrote: >> On Mon, May 06, 2013 at 09:41:22PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote: >>> On 21:29 Mon 06 May , Linus Walleij wrote: >>>> On Sun, May 5, 2013 at 10:22 PM, Jean-Christophe PLAGNIOL-VILLARD >>>> <plagnioj@xxxxxxxxxxxx> wrote: >>>> >>>>> I was thinking to put a jenkins to test Linus HEAD all the time >>>>> And with some automatic test one some hw >>>>> >>>>> to detect it more quick > ... >> My conclusion is that build and boot test systems just don't work in an >> open source environment as no one actively checks the results. Why would >> they - maintainers already have enough to do with reading 6500+ emails a >> month on mailing lists. Why bother going to look at a website as well >> which might give even more work. > > Couldn't such a system email people pro-actively, so nobody had to do > any manual checking? The kisskb(?) build system does that, as does the > "zero day build system" thing from Intel, and I find them quite useful. > Personally, I do the build/test checks manually myself, so if an > automated system were to do it, it'd save me work rather than give me > more work. Yes, this 0day build system rocks. It will pull in specific branches in maintainer branch and do building/automatic code checking like smack/boot testing. If they find any issues, they will send out emails directly to the authors and SoB persons. We just need to add our ARM into to their system for such building/booting test. So for this issue, it should be very easy to find and email to the author. Thanks, -Bryan -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
