From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Borntraeger Subject: Re: [PATCH] autofs4: fix compilation without CONFIG_COMPAT Date: Mon, 27 Feb 2012 08:29:25 +0100 Message-ID: <4F4B30D5.6050305@de.ibm.com> References: <20120221.221609.218135609185671883.davem@davemloft.net> <1329889428.2193.45.camel@perseus.themaw.net> <1329890027.2193.48.camel@perseus.themaw.net> <1329890251.2193.50.camel@perseus.themaw.net> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Linus Torvalds Cc: Andreas Schwab , Ian Kent , David Miller , linux-kernel@vger.kernel.org, "H. Peter Anvin" , autofs@vger.kernel.org, Thomas Meyer , Al Viro , Heiko Carstens , Martin Schwidefsky On 26/02/12 02:31, Linus Torvalds wrote: > > +#else > + > +#define is_compat_task() (0) > + Linus, this breaks 32bit builds of s390 (and maybe others), since several platforms already define a is_compat_task. This macro then destroys the definition of the function making static inline int is_compat_task(void) { return 0; } into static inline int 0 { return 0; } e.g. In file included from arch/s390/mm/fault.c:39:0: /home/autobuild/BUILD/linux-3.3.0-rc5.00060.g203738e.49.x.20120227/arch/s390/include/asm/compat.h:177:38: error: macro "is_compat_task" passed 1 arguments, but takes just 0 /home/autobuild/BUILD/linux-3.3.0-rc5.00060.g203738e.49.x.20120227/arch/s390/include/asm/compat.h:178:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token CC arch/s390/kernel/time.o Christian