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] [thread-next>] [day] [month] [year] [list]
Message-Id: <20120426231203.b1fbc86e26b2c9b426b81a64@canb.auug.org.au>
Date:	Thu, 26 Apr 2012 23:12:03 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	"Luis R. Rodriguez" <mcgrof@...jolero.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Tags for successful compilations of linux-next

Hi Luis,

On Thu, 26 Apr 2012 05:32:13 -0700 "Luis R. Rodriguez" <mcgrof@...jolero.org> wrote:
>
> As a daily consumer of linux-next I'm wondering if there are tags that
> perhaps could be introduced to annotate when a linux-next tag itself
> did successfully compile across all the tests you have for linux-next
> each day. As a consumer of linux-next, for example, I could just take
> those tags to ensure my own snapshots do compile as well. Checking
> with you to see if this is worth it for an extra tag to annotate these
> somehow.

Linux-next has never built for all the test builds we do :-(  However,
(almost) every linux-next release does build for the following:

PowerPC: ppc64_defconfig, allnoconfig, (64bit) allnoconfig, ppc44x_defconfig,
         allyesconfig (fails in the final link)
X86_64: allmodconfig
i386: defconfig
sparc: 32 and 64 bit defconfig

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ