From: swarren@nvidia.com (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: boot/compressed/misc.s: Include <linux/bug.h> to fix build break
Date: Mon, 27 Feb 2012 12:52:30 -0700 [thread overview]
Message-ID: <1330372350-6432-1-git-send-email-swarren@nvidia.com> (raw)
Commmit cf86c17 "kernel.h: doesn't explicitly use bug.h, so don't include
it." caused the following build failure on ARM:
CC arch/arm/boot/compressed/misc.o
In file included from arch/arm/boot/compressed/misc.c:28:0:
arch/arm/mach-tegra/include/mach/uncompress.h: In function 'arch_decomp_setup':
arch/arm/mach-tegra/include/mach/uncompress.h:125:2: error: implicit declaration of function 'BUILD_BUG_ON_ZERO' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
Include <linux/bug.h> to fix that.
This should probably be squashed into commit a3a3a1a "bug.h: add include
of it to various implicit C users".
Signed-off-by: Stephen Warren <swarren@nvidia.com>
---
arch/arm/boot/compressed/misc.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/compressed/misc.c b/arch/arm/boot/compressed/misc.c
index 8e2a8fc..30055be 100644
--- a/arch/arm/boot/compressed/misc.c
+++ b/arch/arm/boot/compressed/misc.c
@@ -18,6 +18,7 @@
unsigned int __machine_arch_type;
+#include <linux/bug.h>
#include <linux/compiler.h> /* for inline */
#include <linux/types.h>
#include <linux/linkage.h>
--
1.7.0.4
next reply other threads:[~2012-02-27 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 19:52 Stephen Warren [this message]
2012-02-27 19:56 ` [PATCH] ARM: boot/compressed/misc.s: Include <linux/bug.h> to fix build break Russell King - ARM Linux
2012-02-27 20:14 ` Stephen Warren
2012-02-29 1:26 ` Paul Gortmaker
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=1330372350-6432-1-git-send-email-swarren@nvidia.com \
--to=swarren@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.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).