From: Olof Johansson <olof@lixom.net>
To: Adrian Bunk <bunk@kernel.org>
Cc: paulus@samba.org, linuxppc-dev@ozlabs.org,
Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] powerpc: proper defconfig for crosscompiles
Date: Sun, 9 Sep 2007 15:40:17 -0500 [thread overview]
Message-ID: <20070909204017.GA7275@lixom.net> (raw)
In-Reply-To: <20070909182117.GJ3563@stusta.de>
On Sun, Sep 09, 2007 at 08:21:17PM +0200, Adrian Bunk wrote:
> The trick for finding the right defconfig is neat, but you forgot to
> provide an i686_defconfig. ;-)
>
> More seriously, cross compiling the defconfig is often useful, e.g. for
> testing the compilation of patches that touch multiple architectures,
> and this patch therefore chooses g5_defconfig if $(CROSS_COMPILE) is
> non-empty.
You should probably use ppc64_defconfig instead, since it's the "superset"
config that will compile a multiplatform kernel.
-Olof
prev parent reply other threads:[~2007-09-09 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-09 18:21 [2.6 patch] powerpc: proper defconfig for crosscompiles Adrian Bunk
2007-09-09 18:39 ` Sam Ravnborg
2007-09-09 20:40 ` Olof Johansson [this message]
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=20070909204017.GA7275@lixom.net \
--to=olof@lixom.net \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sam@ravnborg.org \
/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