From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next build error (at91) - use of bool in mach/arch.h
Date: Tue, 30 Apr 2013 11:33:40 +0200 [thread overview]
Message-ID: <517F8FF4.3050901@atmel.com> (raw)
Hi,
Today I discovered an issue while building linux-next for at91:
CC arch/arm/mach-at91/at91sam9260_devices.o
In file included from /home/nferre/dev/lnx_buid_test/arch/arm/mach-at91/at91sam9260_devices.c:12:0:
/home/nferre/dev/lnx_buid_test/arch/arm/include/asm/mach/arch.h:46:2: error: expected specifier-qualifier-list before ?bool?
It also applies to all non-DT at91 platforms (~ 6 machines).
It seems to be caused by inclusion of commmit
4dbfa9a25367cfa91aec0e56d75a6905d3242cd3 (ARM: Enable selection of
SMP operations at boot time) and its use of the "bool" type.
In fact, we include asm/mach/arch.h file in our at91xxx_devices.c files and
we include it as the first include directive.
So, I am wondering if the best correction is to add the types.h header file
in the asm/mach/arch.h file, like this:
--- a/arch/arm/include/asm/mach/arch.h
+++ b/arch/arm/include/asm/mach/arch.h
@@ -8,6 +8,8 @@
* published by the Free Software Foundation.
*/
+#include <linux/types.h>
+
#ifndef __ASSEMBLY__
struct tag;
or if a better option would be to re-arrange the include directives in
various at91xxx_devices.c files?
Thanks, bye,
--
Nicolas Ferre
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Marc Zyngier <marc.zyngier@arm.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Jon Medhurst <tixy@linaro.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
"Jean-Christophe PLAGNIOL-VILLARD" <plagnioj@jcrosoft.com>,
Ludovic Desroches <ludovic.desroches@atmel.com>,
Nicolas Pitre <nicolas.pitre@linaro.org>
Subject: linux-next build error (at91) - use of bool in mach/arch.h
Date: Tue, 30 Apr 2013 11:33:40 +0200 [thread overview]
Message-ID: <517F8FF4.3050901@atmel.com> (raw)
Hi,
Today I discovered an issue while building linux-next for at91:
CC arch/arm/mach-at91/at91sam9260_devices.o
In file included from /home/nferre/dev/lnx_buid_test/arch/arm/mach-at91/at91sam9260_devices.c:12:0:
/home/nferre/dev/lnx_buid_test/arch/arm/include/asm/mach/arch.h:46:2: error: expected specifier-qualifier-list before ‘bool’
It also applies to all non-DT at91 platforms (~ 6 machines).
It seems to be caused by inclusion of commmit
4dbfa9a25367cfa91aec0e56d75a6905d3242cd3 (ARM: Enable selection of
SMP operations at boot time) and its use of the "bool" type.
In fact, we include asm/mach/arch.h file in our at91xxx_devices.c files and
we include it as the first include directive.
So, I am wondering if the best correction is to add the types.h header file
in the asm/mach/arch.h file, like this:
--- a/arch/arm/include/asm/mach/arch.h
+++ b/arch/arm/include/asm/mach/arch.h
@@ -8,6 +8,8 @@
* published by the Free Software Foundation.
*/
+#include <linux/types.h>
+
#ifndef __ASSEMBLY__
struct tag;
or if a better option would be to re-arrange the include directives in
various at91xxx_devices.c files?
Thanks, bye,
--
Nicolas Ferre
next reply other threads:[~2013-04-30 9:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 9:33 Nicolas Ferre [this message]
2013-04-30 9:33 ` linux-next build error (at91) - use of bool in mach/arch.h Nicolas Ferre
2013-04-30 9:39 ` Geert Uytterhoeven
2013-04-30 9:39 ` Geert Uytterhoeven
2013-04-30 11:58 ` Stefano Stabellini
2013-04-30 11:58 ` Stefano Stabellini
2013-04-30 12:40 ` Nicolas Ferre
2013-04-30 12:40 ` Nicolas Ferre
2013-04-30 15:15 ` Nicolas Pitre
2013-04-30 15:15 ` Nicolas Pitre
2013-04-30 15:59 ` Stefano Stabellini
2013-04-30 15:59 ` Stefano Stabellini
2013-04-30 12:38 ` [PATCH] ARM: add the "bool" type definition to asm/mach/arch.h Nicolas Ferre
2013-04-30 12:38 ` Nicolas Ferre
2013-04-30 14:05 ` Stefano Stabellini
2013-04-30 14:05 ` Stefano Stabellini
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=517F8FF4.3050901@atmel.com \
--to=nicolas.ferre@atmel.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 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.