From: Randy Dunlap <randy.dunlap@oracle.com>
To: Chris Snook <csnook@redhat.com>
Cc: Tony Breeds <tony@bakeyournoodle.com>,
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: Thu, 14 Feb 2008 19:13:28 -0800 [thread overview]
Message-ID: <20080214191328.75b6e1bf.randy.dunlap@oracle.com> (raw)
In-Reply-To: <47B4FEBC.2020700@redhat.com>
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
next prev parent reply other threads:[~2008-02-15 3:14 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 [this message]
2008-02-15 12:42 ` Michael Ellerman
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=20080214191328.75b6e1bf.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=csnook@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tony@bakeyournoodle.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®