From: Shane McDonald <mcdonald.shane@gmail.com>
To: linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: [PATCH] MIPS: Fix build failure of msp71xx default configuration
Date: Thu, 03 Jan 2013 21:40:03 -0600 [thread overview]
Message-ID: <E1Tqy8Z-0003Uc-Cm@localhost> (raw)
The msp71xx default configuration fails to compile in Linux 3.8-rc2:
In file included from /home/shane/linux-mips/linux/arch/mips/include/asm/bitops.h:22,
from include/linux/bitops.h:22,
from include/linux/kernel.h:10,
from include/asm-generic/bug.h:13,
from /home/shane/linux-mips/linux/arch/mips/include/asm/bug.h:41,
from include/linux/bug.h:4,
from include/linux/page-flags.h:9,
from kernel/bounds.c:9:
/home/shane/linux-mips/linux/arch/mips/include/asm/war.h:12:17: error: war.h: No such file or directory
This is because the Platform file points at the incorrect include file
location, and therefore the war.h file cannot be found.
This patch changes the Platform file to point to the correct location.
Caused by a combination of the following lmo-only patches:
13a347ef60c68e490809dad8fcf79c25eabc4d58 [MIPS: MSP71xx: Move code.]
a89c0370cb5429891d49abcc66f93c63b43c7dbe
[MIPS: Fix make distclean after moving the PMC-Sierra code.]
Signed-off-by: Shane McDonald <mcdonald.shane@gmail.com>
---
arch/mips/pmcs-msp71xx/Platform | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/mips/pmcs-msp71xx/Platform b/arch/mips/pmcs-msp71xx/Platform
index e42a4d6..9a86e29 100644
--- a/arch/mips/pmcs-msp71xx/Platform
+++ b/arch/mips/pmcs-msp71xx/Platform
@@ -2,6 +2,6 @@
# PMC-Sierra MSP SOCs
#
platform-$(CONFIG_PMC_MSP) += pmcs-msp71xx/
-cflags-$(CONFIG_PMC_MSP) += -I$(srctree)/arch/mips/include/asm/pmc-sierra \
+cflags-$(CONFIG_PMC_MSP) += -I$(srctree)/arch/mips/include/asm/pmc-sierra/msp71xx \
-mno-branch-likely
load-$(CONFIG_PMC_MSP) += 0xffffffff80100000
--
1.7.2.5
reply other threads:[~2013-01-04 3:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1Tqy8Z-0003Uc-Cm@localhost \
--to=mcdonald.shane@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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.