public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Dabney <smurf@osdlab.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: Nathan Dabney <smurf@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Kernel Releases
Date: Sun, 25 Nov 2001 11:03:15 -0800	[thread overview]
Message-ID: <20011125110315.A17688@osdlab.org> (raw)
In-Reply-To: <20011125012507.C6414@osdlab.org> <12023.1006683861@ocs3.intra.ocs.com.au>
In-Reply-To: <12023.1006683861@ocs3.intra.ocs.com.au>

On Sun, Nov 25, 2001 at 09:24:21PM +1100, Keith Owens wrote:
> On Sun, 25 Nov 2001 01:25:07 -0800, 
> Nathan Dabney <smurf@osdlab.org> wrote:
> >We will be running all the available tests (until that list gets too large
> >to be possible) on each kernel the morning after it's released.
> 
> Have you been following the kbuild 2.5 developments[1]?  Linus has
> agreed that this change will go in early in the 2.5 cycle, that will
> impact on all automated testing for 2.5.  There will be both good and
> bad impacts, the bad is the initial changeover, the good is a much
> cleaner build process and the ability to build multiple configurations
> from a single source tree.
> 
> [1] http://sourceforge.net/projects/kbuild/

Yes, we will be able to add another method for (auto) kernel configuration when
this becomes an issue (hopefully RSN).

Currently the method we use to "sanitize" submitted kernel configs for our
hardware is as reliable as you can get under CML1.  It doesn't however, give
us a good way to build multiple configurations.

-Nathan

  parent reply	other threads:[~2001-11-25 19:03 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-25  5:37 Kernel Releases Dan Kegel
2001-11-25  9:25 ` Nathan Dabney
2001-11-25 10:24   ` Keith Owens
2001-11-25 13:34     ` Phil Howard
2001-11-25 19:03     ` Nathan Dabney [this message]
     [not found] <Pine.LNX.4.33.0111261807570.489-100000@mikeg.weiden.de>
2001-11-27 18:08 ` vda
2001-11-27 16:58   ` Mike Galbraith
     [not found] <fa.dac7a7v.1hkofg8@ifi.uio.no>
2001-11-27 17:53 ` Giacomo Catenazzi
  -- strict thread matches above, loose matches on Subject: below --
2001-11-27 17:25 Dan Kegel
2001-11-27 17:36 ` François Cami
2001-11-27 17:38   ` Dan Kegel
2001-11-27 18:13     ` Vitaly Luban
2001-11-28 16:23     ` Horst von Brand
2001-11-28 19:17       ` Mike Fedyk
2001-11-26 10:46 Martin Knoblauch
2001-11-26 15:27 ` John Jasen
2001-11-26 20:36   ` Horst von Brand
2001-11-27  2:40     ` Gerhard Mack
2001-11-25  4:27 David Relson
2001-11-25  5:49 ` John Alvord
2001-11-25  6:34   ` CaT
2001-11-25 14:12   ` John Jasen
2001-11-26  7:15     ` John Alvord
2001-11-25 15:46   ` Eric W. Biederman
2001-11-25 16:23     ` Nathan Walp
2001-11-26 21:03     ` Bill Davidsen
2001-11-25 19:55 ` Phil Sorber
2001-11-26  9:22 ` Allan Sandfeld
2001-11-26 14:51   ` Ian Stirling
2001-11-26 15:02     ` Rik van Riel
2001-11-26 19:11       ` Ian Stirling
2001-11-26 19:55       ` vda
2001-11-26 20:42 ` Bill Davidsen
2001-11-27  4:21   ` Mike Fedyk
2001-11-27  9:50   ` Helge Hafting

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=20011125110315.A17688@osdlab.org \
    --to=smurf@osdlab.org \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smurf@osdl.org \
    /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