On 20:54 Mon 06 May , 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 > > > > > > Hm yeah, I think I need a broader diversity of testsystems too ... I have this > > > nice Chromebook so I thought if I could get a mainline kernel running on > > > it I'd have a bigger coverage as well. > > > > Maybe we could all work together to setup such automatic testing tool > > > > I mean all vendors > > Don't bother. We had one, Simtec's Vince Sanders gave us the build side. > No one was interested. No one took any notice of it. I have one for a > limited number of platforms - it even boots the resulting kernels on real > hardware. The only person who looks at it is me. Again, just one person, > so little value. Could you push the build failled on the arm ML or a specific ML I'm really intresting I hate to brake platform support specialy yours > > And that same thing will appy to anything else setup by anyone else. > > It's a good idea, but it only really works if people can be bothered to > derive value from it by checking the results. We can have enforce policy if some brake something again and agian we can do as Greg did for one of the Linaro dev. Force the patch to be double check by a senior Maintainter. And I think it will help Maintainer (Specially subsystem) to detect runtime bug when applying code they can not test So I really hope we could change this and make it work Maybe as you rsaid it will not work but I'm willing to try one more time -- 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
