linux-kernel - Re: [PATCH] remove 556 unneeded #includes of sched.h

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061228214830.GF20596@flint.arm.linux.org.uk>
Date:	Thu, 28 Dec 2006 21:48:30 +0000
From:	Russell King <rmk+lkml@....linux.org.uk>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Tim Schmielau <tim@...sik3.uni-rostock.de>,
	Al Viro <viro@....linux.org.uk>, Andrew Morton <akpm@...l.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] remove 556 unneeded #includes of sched.h

On Thu, Dec 28, 2006 at 01:32:46PM -0800, Randy Dunlap wrote:
> On Thu, 28 Dec 2006 21:34:38 +0000 Russell King wrote:
> > 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?

Given that it takes about 8 to 12 hours to do a build cycle, that's
not practical.  The only real solution is for us to accept that
breakage will occur (and be prepared to keep a steady stream of
fixes heading into Linus' tree - which has been ruled out by Linus)
or J. Random Developer has to build a set of affected ARM defconfigs
themselves.

Or alternatively the guy who's running kautobuild needs an amount of
rather powerful donated hardware to stubstantially increase it's
throughput.

Or cross-gcc needs to be optimised to compile faster.

I don't see any of the above happening, so...

-- 
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/