[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080216003136.GG31474@flint.arm.linux.org.uk>
Date: Sat, 16 Feb 2008 00:31:36 +0000
From: Russell King <rmk+lkml@....linux.org.uk>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: 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 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 ;)
Maybe - it's a lowly 2.6GHz P4 with 1GB RAM, ICH5, and SATA disk.
> 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?
It will certainly improve the situation significantly, and pick up
on some non-ARM problems like (badge4_defconfig, since 2.6.24-git2):
drivers/built-in.o: In function `v4l2_i2c_attach':
drivers/media/video/v4l2-common.c:1035: undefined reference to `i2c_attach_client'
Currently, the defconfigs known to fail (long term) in Linus' tree
are clps7500_defconfig and trizeps4_defconfig - the former I'm tempted
to remove, the latter seems to be because the PCMCIA changes were lost
on the linux-pcmcia list and the trizeps folk have probably given up.
--
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