From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mx51: Fix build error due to missing include of <linux/bug.h>
Date: Tue, 28 Feb 2012 12:53:36 +0000 [thread overview]
Message-ID: <20120228125336.GA3617@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1330431110-22020-1-git-send-email-fabio.estevam@freescale.com>
On Tue, Feb 28, 2012 at 09:11:50AM -0300, Fabio Estevam wrote:
> Fix the following build error:
>
> arch/arm/mach-imx/cpu_op-mx51.c: In function 'mx51_get_cpu_op':
> arch/arm/mach-imx/cpu_op-mx51.c:27: error: implicit declaration of function 'BUILD_BUG_ON_ZERO'
I think having the asm/bug.h replaced with linux/bug.h in linux/kernel.h
would be a better solution.
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> This applies against linux-next
>
> arch/arm/mach-imx/cpu_op-mx51.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-imx/cpu_op-mx51.c b/arch/arm/mach-imx/cpu_op-mx51.c
> index 9d34c3d..9a4f77a 100644
> --- a/arch/arm/mach-imx/cpu_op-mx51.c
> +++ b/arch/arm/mach-imx/cpu_op-mx51.c
> @@ -14,6 +14,7 @@
> #include <linux/types.h>
> #include <mach/hardware.h>
> #include <linux/kernel.h>
> +#include <linux/bug.h>
>
> static struct cpu_op mx51_cpu_op[] = {
> {
> --
> 1.7.1
>
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2012-02-28 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 12:11 [PATCH] ARM: mx51: Fix build error due to missing include of <linux/bug.h> Fabio Estevam
2012-02-28 12:53 ` Russell King - ARM Linux [this message]
2012-02-28 13:03 ` Fabio Estevam
2012-02-28 13:21 ` Russell King - ARM Linux
2012-02-28 13:25 ` Fabio Estevam
2012-02-28 23:52 ` Paul Gortmaker
2012-02-29 0:06 ` Russell King - ARM Linux
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=20120228125336.GA3617@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).