LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Michael Ellerman" <michael@ellerman.id.au>
To: "Chris Snook" <csnook@redhat.com>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next build status
Date: Fri, 15 Feb 2008 23:42:03 +1100	[thread overview]
Message-ID: <dc1166600802150442w7787b372pb91be1f51919f00@mail.gmail.com> (raw)
In-Reply-To: <47B4E9CB.3090708@redhat.com>

On Fri, Feb 15, 2008 at 12:24 PM, Chris Snook <csnook@redhat.com> wrote:
> Stephen Rothwell wrote:
>  > Hi all,
>  >
>  > Initial status can be seen here
>  > http://kisskb.ellerman.id.au/kisskb/branch/9/ (I hope to make a better
>  > URL soon).  Suggestions for more compiler/config combinations are
>  > welcome, but we can't necessarily commit to fulfilling all you
>  > wishes.  :-)
>  >
>
>  i386 allmodconfig please.
>
>  Also, I highly recommend adding some randconfig builds, at least one 32-bit arch
>  and one 64-bit arch.  Any given randconfig build is not particularly likely to
>  catch bugs that would be missed elsewhere, but doing them daily for two months
>  will catch a lot of things before they get released.  The catch, of course, is
>  that you have to actually save the .config for this to be useful, which might
>  require a slight modification to your scripts.

It does save the configs, so randconfig might be an option. I'll look
at it next week.

cheers

      parent reply	other threads:[~2008-02-15 12:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15  0:42 Stephen Rothwell
2008-02-15  1:09 ` Adrian Bunk
2008-02-15  1:24 ` Chris Snook
2008-02-15  2:05   ` Tony Breeds
2008-02-15  2:53     ` Chris Snook
2008-02-15  3:13       ` Randy Dunlap
2008-02-15 12:42   ` Michael Ellerman [this message]

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=dc1166600802150442w7787b372pb91be1f51919f00@mail.gmail.com \
    --to=michael@ellerman.id.au \
    --cc=csnook@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --subject='Re: linux-next build status' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).