linux-kernel - Re: linux-next build status

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] [day] [month] [year] [list]

Message-ID: <dc1166600802150442w7787b372pb91be1f51919f00@mail.gmail.com>
Date:	Fri, 15 Feb 2008 23:42:03 +1100
From:	"Michael Ellerman" <michael@...erman.id.au>
To:	"Chris Snook" <csnook@...hat.com>
Cc:	"Stephen Rothwell" <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next build status

On Fri, Feb 15, 2008 at 12:24 PM, Chris Snook <csnook@...hat.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
--
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/