[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20090114033120.0333b392.sfr@canb.auug.org.au>
Date: Wed, 14 Jan 2009 03:31:20 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Ingo Molnar <mingo@...e.hu>
Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-next@...r.kernel.org, Rusty Russell <rusty@...tcorp.com.au>,
Mike Travis <travis@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
"David S. Miller" <davem@...emloft.net>,
LKML <linux-kernel@...r.kernel.org>,
Paul Mackerras <paulus@...ba.org>, linuxppc-dev@...abs.org
Subject: Re: linux-next: origin tree build failure
Hi Ingo,
On Mon, 12 Jan 2009 10:32:14 +0100 Ingo Molnar <mingo@...e.hu> wrote:
>
> * Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> > > It slipped through because it didnt get caught in build tests because
> > > cpufreq isnt enabled in the powerpc defconfig.
> >
> > Which is one of the reasons we have linux-next: "integration testing".
>
> Build bugs slipped through that net too in the past.
Of course they have.
> And we dont really want developers and maintainers to rely on an external
> middle man facility to be able to submit patches. So the best method is to
> make the defconfigs good enough to catch everyday build bugs. Random
> testing and linux-next can then catch the weird special cases as well.
linux-next is merely a tool - it can't catch anything if you don't use it.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists