[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <517FBBBB.6060003@atmel.com>
Date: Tue, 30 Apr 2013 14:40:27 +0200
From: Nicolas Ferre <nicolas.ferre@...el.com>
To: Stefano Stabellini <stefano.stabellini@...citrix.com>
CC: Geert Uytterhoeven <geert@...ux-m68k.org>,
Marc Zyngier <marc.zyngier@....com>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Russell King - ARM Linux <linux@....linux.org.uk>,
Jon Medhurst <tixy@...aro.org>,
Linux Kernel list <linux-kernel@...r.kernel.org>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>,
Ludovic Desroches <ludovic.desroches@...el.com>,
Nicolas Pitre <nicolas.pitre@...aro.org>
Subject: Re: linux-next build error (at91) - use of bool in mach/arch.h
On 04/30/2013 01:58 PM, Stefano Stabellini :
> On Tue, 30 Apr 2013, Geert Uytterhoeven wrote:
>> On Tue, Apr 30, 2013 at 11:33 AM, Nicolas Ferre <nicolas.ferre@...el.com> wrote:
>>> 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?
>>
>> Include files should be self-contained, so asm/mach/arch.h is the right place.
>
> Nicolas,
> are you happy to come up with a proper patch to fix the issue?
Yep, sent now.
Bye,
--
Nicolas Ferre
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists