From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Rothwell Subject: Re: linux-next: build failure after merge of the aio tree Date: Thu, 4 Feb 2016 13:19:59 +1100 Message-ID: <20160204131959.6695c7bf@canb.auug.org.au> References: <20160112164034.0fe945a7@canb.auug.org.au> <20160112163835.GD347@kvack.org> <20160127134024.0fababf6@canb.auug.org.au> <20160129113056.GP10826@n2100.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from ozlabs.org ([103.22.144.67]:52776 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755275AbcBDCUB (ORCPT ); Wed, 3 Feb 2016 21:20:01 -0500 In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Benjamin LaHaise Cc: Geert Uytterhoeven , Russell King - ARM Linux , Linux-Next , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Hi Benjamin, On Fri, 29 Jan 2016 13:03:39 +0100 Geert Uytterhoeven wrote: > > On Fri, Jan 29, 2016 at 12:30 PM, Russell King - ARM Linux > wrote: > >> Background: new aio code is adding __get_user() calls referencing 64 > >> bit quantities (__u64 and __s64). > > > > There's lots more architectures which do not support 64-bit get_user() > > _or_ __get_user(): avr32, blackfin, metag for example, and m68k which > > has this interesting thing "/* case 8: disabled because gcc-4.1 has a > > broken typeof \" in its *get_user() implementation. > > And if you enable it again, you get lots of "warning: cast to pointer from > integer of different size", like you mentioned. Any thoughts? I am still using the version of tha aio tree from next-20160111. -- Cheers, Stephen Rothwell