public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Randy Dunlap <randy.dunlap@oracle.com>
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 21:48:30 +0000	[thread overview]
Message-ID: <20061228214830.GF20596@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20061228133246.ad820c6a.randy.dunlap@oracle.com>

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:

  reply	other threads:[~2006-12-28 21:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-28 20:27 [PATCH] remove 556 unneeded #includes of sched.h 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
2006-12-28 21:48             ` Russell King [this message]
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=20061228214830.GF20596@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --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