[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080214191328.75b6e1bf.randy.dunlap@oracle.com>
Date: Thu, 14 Feb 2008 19:13:28 -0800
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Chris Snook <csnook@...hat.com>
Cc: Tony Breeds <tony@...eyournoodle.com>,
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 Thu, 14 Feb 2008 21:53:48 -0500 Chris Snook wrote:
> 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.
x86_64 doesn't compile ISA drivers (last time I checked).
Could be a few other subtle differences.
---
~Randy
--
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