From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760932Ab3D3P7d (ORCPT ); Tue, 30 Apr 2013 11:59:33 -0400 Received: from smtp02.citrix.com ([66.165.176.63]:2874 "EHLO SMTP02.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758280Ab3D3P7a (ORCPT ); Tue, 30 Apr 2013 11:59:30 -0400 X-IronPort-AV: E=Sophos;i="4.87,582,1363132800"; d="scan'208";a="21357389" Date: Tue, 30 Apr 2013 16:59:26 +0100 From: Stefano Stabellini X-X-Sender: sstabellini@kaball.uk.xensource.com To: Nicolas Pitre CC: Stefano Stabellini , Geert Uytterhoeven , Nicolas Ferre , Marc Zyngier , linux-arm-kernel , Russell King - ARM Linux , Jon Medhurst , Linux Kernel list , Jean-Christophe PLAGNIOL-VILLARD , Ludovic Desroches Subject: Re: linux-next build error (at91) - use of bool in mach/arch.h In-Reply-To: Message-ID: References: <517F8FF4.3050901@atmel.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 30 Apr 2013, Nicolas Pitre wrote: > On Tue, 30 Apr 2013, Stefano Stabellini wrote: > > > On Tue, 30 Apr 2013, Geert Uytterhoeven wrote: > > > On Tue, Apr 30, 2013 at 11:33 AM, Nicolas Ferre 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 > > > > + > > > > #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? > > I'd prefer if you just folded the above include into the original patch, > unless this has been pulled already. No, I'll exploit the opportunity to resend the patch series and issue a PULL request for the arm-soc tree.