From: Randy Dunlap <randy.dunlap@oracle.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Tim Schmielau <tim@physik3.uni-rostock.de>,
Al Viro <viro@ftp.linux.org.uk>, Andrew Morton <akpm@osdl.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] remove 556 unneeded #includes of sched.h
Date: Thu, 28 Dec 2006 13:32:46 -0800 [thread overview]
Message-ID: <20061228133246.ad820c6a.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20061228213438.GD20596@flint.arm.linux.org.uk>
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
next prev parent reply other threads:[~2006-12-28 21:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 20:27 Tim Schmielau
2006-12-28 20:36 ` Tim Schmielau
2006-12-28 20:46 ` Andrew Morton
2006-12-28 20:58 ` Randy Dunlap
2006-12-28 21:10 ` Tim Schmielau
2006-12-28 20:58 ` Tim Schmielau
2006-12-28 21:08 ` Al Viro
2006-12-28 21:18 ` Tim Schmielau
2006-12-28 21:34 ` Russell King
2006-12-28 21:32 ` Randy Dunlap [this message]
2006-12-28 21:48 ` Russell King
2006-12-28 21:53 ` Tim Schmielau
2006-12-28 22:23 ` Russell King
2006-12-28 22:27 ` Tim Schmielau
2006-12-29 0:10 ` Randy Dunlap
2006-12-29 0:37 ` Tim Schmielau
2006-12-29 0:31 ` Randy Dunlap
2006-12-29 10:40 ` Tim Schmielau
2006-12-28 21:42 ` Tim Schmielau
2006-12-29 10:23 ` [updated PATCH] remove 555 " Tim Schmielau
2006-12-29 10:43 ` Tim Schmielau
2006-12-30 17:19 ` Russell King
2007-01-23 6:15 ` Oleg Verych
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061228133246.ad820c6a.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=tim@physik3.uni-rostock.de \
--cc=viro@ftp.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome