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  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]
Date:	Thu, 14 Feb 2008 21:53:48 -0500
From:	Chris Snook <csnook@...hat.com>
To:	Tony Breeds <tony@...eyournoodle.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

Tony Breeds wrote:
> On Thu, Feb 14, 2008 at 08:24:27PM -0500, Chris Snook 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.
> 
> Wont i386 allmodconfig be equivalent to x86_64 allmodconfig?

Only if there are no bugs.

Driver code is most likely to trip over bitness/endianness bugs, and 
you've already got allmodconfig builds for be32, be64, and le64 
architectures.  Adding an le32 architecture (i386) completes the 
coverage of these basic categories.

	-- Chris
--
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/

Powered by blists - more mailing lists