[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080216080841.GA19396@flint.arm.linux.org.uk>
Date: Sat, 16 Feb 2008 08:08:41 +0000
From: Russell King <rmk+lkml@....linux.org.uk>
To: Alexey Dobriyan <adobriyan@...il.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, sfr@...b.auug.org.au,
linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
linux-arch@...r.kernel.org, torvalds@...ux-foundation.org
Subject: Re: Announce: Linux-next (Or Andrew's dream :-))
On Sat, Feb 16, 2008 at 03:42:49AM +0300, Alexey Dobriyan wrote:
> On Fri, Feb 15, 2008 at 04:21:21PM -0800, Andrew Morton wrote:
> > On Sat, 16 Feb 2008 00:09:43 +0000
> > Russell King <rmk+lkml@....linux.org.uk> wrote:
> >
> > > For reference, even _I_ don't build test the entire set of ARM defconfigs -
> > > at about 7 minutes a build, 75 defconfigs, that's about 9 hours... I
> > > just build those which are important to myself, hope that the others are
> > > fine, and rely on kautobuild finding any breakage.
> > >
> >
> > you need a better box ;)
> >
> > cerfcube_defconfig: 35 seconds
> > carmeva_defconfig: 23 seconds
> > spitz_defconfig (one of the biggest): 45 seconds
> >
> > so would a stupid `for i in arch/arm/configs/*' script be sufficient
> > coverage?
>
> I do this wildcard together with
>
> yes '' | make ARCH=arm ... oldconfig
> make
>
> Sans toolchain issues, it's pretty good -- Russell larts you when some
> defconfig becomes broken anyway. :^)
Only when I check the kautobuild website - which I've not been doing
regularly since about end of November, and it only covers Linus'
kernels.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists