From: "H. Peter Anvin" <hpa@zytor.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Sam Ravnborg <sam@ravnborg.org>,
linux-arch@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>,
Ian Campbell <icampbell@arcom.com>,
Mike Frysinger <vapier@gentoo.org>,
Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Hirokazu Takata <takata@linux-m32r.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Kyle McMartin <kyle@mcmartin.ca>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Paul Mundt <lethal@linux-sh.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH/RFC] kbuild: use INSTALLKERNEL to select customized installkernel script
Date: Mon, 20 Jul 2009 18:22:43 -0700 [thread overview]
Message-ID: <4A651863.6090009@zytor.com> (raw)
In-Reply-To: <20090720221120.GG11151@n2100.arm.linux.org.uk>
Russell King - ARM Linux wrote:
>
> That's a good thing in some ways and a bad thing in others. Having
> it guarantee to fail if you try installing an ARM kernel onto an
> x86 machine is definitely a good thing. That said, it's not something
> I've ever accidentally done.
>
I guess we could have it error out if you are building a non-native
architecture but don't set CROSS_COMPILE. Either that or we could
default $INSTALLKERNEL to $(CROSS_COMPILE)installkernel, which would be
backwards compatible.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-07-21 1:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 20:11 [PATCH/RFC] kbuild: use INSTALLKERNEL to select customized installkernel script Sam Ravnborg
2009-07-20 20:19 ` H. Peter Anvin
2009-07-20 20:49 ` Paul Mundt
2009-07-20 22:11 ` Russell King - ARM Linux
2009-07-21 1:22 ` H. Peter Anvin [this message]
2009-07-21 7:18 ` Sam Ravnborg
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=4A651863.6090009@zytor.com \
--to=hpa@zytor.com \
--cc=benh@kernel.crashing.org \
--cc=fenghua.yu@intel.com \
--cc=geert@linux-m68k.org \
--cc=icampbell@arcom.com \
--cc=kyle@mcmartin.ca \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sam@ravnborg.org \
--cc=schwidefsky@de.ibm.com \
--cc=takata@linux-m32r.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=vapier@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.