Re: [PATCH] remove 556 unneeded #includes of sched.h
From: Randy Dunlap
Date: Thu Dec 28 2006 - 16:41:22 EST
On Thu, 28 Dec 2006 21:34:38 +0000 Russell King wrote:
> On Thu, Dec 28, 2006 at 10:18:12PM +0100, Tim Schmielau wrote:
> > On Thu, 28 Dec 2006, Al Viro wrote:
> >
> > > Uh-huh. How much of build coverage have you got with it?
> >
> > Well, as said in the patch description, I compiled alpha, arm, i386, ia64,
> > mips, powerpc, and x86_64 with allnoconfig, defconfig, allmodconfig, and
> > allyesconfig as well as a few randconfigs on x86_64. I also checked that
> > no new warnings were introduced by the patch.
>
> That would not have covered the following drivers in this patch on ARM
> then:
>
> acorn/*
> nwflash
> i2c-iop3xx
> i2c-s3c2410
> ether1
> ether3
> etherh
> omap_cf
> pxa2xx_lubbock
> sa1100_badge4
> sa1100_cerf
> sa1100_h3600
> sa1100_jornada720
> sa1100_neponset
> sa1100_shannon
> sa1100_simpad
> acornscsi
> arxescsi
> cumana_1
> cumana_2
> ecoscsi
> eesox
> fas216
> oak
> powertec
> at91_udc
> omap_udc
> pxa2xx_udc
> zaurus
>
> To cover these, you need to build at least rpc_defconfig, lubbock_defconfig,
> netwinder_defconfig, badge4_defconfig, cerf_defconfig, ...etc...
>
> The whole "all*config" idea on ARM is utterly useless - you can _not_
> get build coverage that way.
Uh, can J. Random Developer submit patches to the ARM build system
for testing?
---
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/