From: Segher Boessenkool <segher@kernel.crashing.org>
To: linuxppc-dev@ozlabs.org
Subject: [PATCH 3/3] powerpc: Don't run prom_init_check for arch/ppc builds
Date: Wed, 7 May 2008 00:58:50 +0200 [thread overview]
Message-ID: <d65aa60aa955433e26e1791e197c533e7a0cd8c4.1210114487.git.segher@kernel.crashing.org> (raw)
In-Reply-To: <3b9b7dce6551e43c8fca4a1a3d4bff5a5b78312b.1210114487.git.segher@kernel.crashing.org>
In-Reply-To: <cf74cd88187bdd9378fbb0a0ff7d53ac3a7b23d2.1210114487.git.segher@kernel.crashing.org>
arch/ppc doesn't have prom_init.o (anymore).
Signed-off-by: Segher Boessenkool <segher@kernel.crashing.org>
---
arch/powerpc/kernel/Makefile | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/kernel/Makefile b/arch/powerpc/kernel/Makefile
index d14cebf..2346d27 100644
--- a/arch/powerpc/kernel/Makefile
+++ b/arch/powerpc/kernel/Makefile
@@ -105,6 +105,9 @@ PHONY += systbl_chk
systbl_chk: $(src)/systbl_chk.sh $(obj)/systbl_chk.i
$(call cmd,systbl_chk)
+
+ifeq ($(CONFIG_PPC_MERGE),y)
+
$(obj)/built-in.o: prom_init_check
quiet_cmd_prom_init_check = CALL $<
@@ -114,4 +117,7 @@ PHONY += prom_init_check
prom_init_check: $(src)/prom_init_check.sh $(obj)/prom_init.o
$(call cmd,prom_init_check)
+endif
+
+
clean-files := vmlinux.lds
--
1.5.5.23.g2a5f.dirty
next prev parent reply other threads:[~2008-05-06 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 22:58 Fix arch/ppc builds Segher Boessenkool
2008-05-06 22:58 ` [PATCH 1/3] ppc: Use ebony_defconfig for defconfig Segher Boessenkool
2008-05-06 22:58 ` [PATCH 2/3] ppc: Include <asm/cacheflush.h> in kernel/ppc_ksyms.c Segher Boessenkool
2008-05-06 22:58 ` Segher Boessenkool [this message]
2008-05-11 21:13 ` Fix arch/ppc builds Josh Boyer
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=d65aa60aa955433e26e1791e197c533e7a0cd8c4.1210114487.git.segher@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).