From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762590AbbA3QPt (ORCPT ); Fri, 30 Jan 2015 11:15:49 -0500 Received: from down.free-electrons.com ([37.187.137.238]:40662 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1762374AbbA3QPr convert rfc822-to-8bit (ORCPT ); Fri, 30 Jan 2015 11:15:47 -0500 Date: Fri, 30 Jan 2015 17:15:38 +0100 From: Boris Brezillon To: Guenter Roeck , David Airlie Cc: Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Matthew Wilcox , Linus Torvalds , Oleksij Rempel , "dri-devel@lists.freedesktop.org" Subject: Re: linux-next: Tree for Jan 30 (build failures) Message-ID: <20150130171538.0facb9b1@bbrezillon> In-Reply-To: <20150130142520.GA6872@roeck-us.net> References: <20150130180209.2bd86cc4@canb.auug.org.au> <20150130142520.GA6872@roeck-us.net> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.23; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Guenter, On Fri, 30 Jan 2015 06:25:20 -0800 Guenter Roeck wrote: > On Fri, Jan 30, 2015 at 06:02:09PM +1100, Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20150129: > > > > The arm-soc gained conflicts against the arm-current and arm trees. > > > > The spi tree gained a build failure for which I reverted a commit. > > > > Non-merge commits (relative to Linus' tree): 6300 > > 6348 files changed, 255117 insertions(+), 131620 deletions(-) > > > > ---------------------------------------------------------------------------- > > Build failures below. I copied the culprits (including Linus ;-). > > Guenter > > === > Building arc:defconfig ... failed > Building arc:tb10x_defconfig ... failed > -------------- > Error log: > arch/arc/mm/fault.c: In function 'do_page_fault': > arch/arc/mm/fault.c:164: error: 'VM_FAULT_SIGSEV' undeclared > > Typo. Caused by 33692f27597f ("vm: add VM_FAULT_SIGSEGV handling support"), > from mainline. I submitted a patch. > > === > Building mips:allmodconfig ... failed > -------------- > Error log: > > fs/built-in.o: In function `dax_fault': > (.text+0x5e284): undefined reference to `copy_user_page' > > Caused by 4927b7d77c001 ("dax,ext2: replace the XIP page fault handler with the > DAX page fault handler"). Looks like copy_user_page does not exist in mips. > > === > Building sparc64:allmodconfig ... failed > -------------- > Error log: > drivers/built-in.o: In function `asm9260_timer_init': > asm9260_timer.c:(.init.text+0x60d4): undefined reference to `of_io_request_and_map' > > Caused by e4940cd76934 ("ARM: clocksource: add asm9260_timer driver"). > of_io_request_and_map does not exist for the sparc architecture. > Maybe that driver should depend on ARM or at least on !SPARC ? > > === > Building xtensa:allmodconfig ... failed > -------------- > Error log: > drivers/gpu/drm/drm_gem_cma_helper.c: In function ‘drm_gem_cma_create’: > drivers/gpu/drm/drm_gem_cma_helper.c:110:2: error: implicit declaration of function ‘dma_alloc_writecombine’ > drivers/gpu/drm/drm_gem_cma_helper.c: In function ‘drm_gem_cma_free_object’: > drivers/gpu/drm/drm_gem_cma_helper.c:193:3: error: implicit declaration of function ‘dma_free_writecombine’ > drivers/gpu/drm/drm_gem_cma_helper.c: In function ‘drm_gem_cma_mmap_obj’: > drivers/gpu/drm/drm_gem_cma_helper.c:330:2: error: implicit declaration of function ‘dma_mmap_writecombine’ > > Caused by 1a396789f65a2 ("drm: add Atmel HLCDC Display Controller support"). > It selects DRM_KMS_CMA_HELPER which selects DRM_GEM_CMA_HELPER which needs > the missing dma functions. Those are not supported on xtensa (HAVE_DMA_ATTRS > is not set for xtensa). Maybe the controller should depend on HAVE_DMA_ATTRS. I fixed that one a week ago: [1]. I'm Adding Dave and the dri-devel ML in Cc, apart from that I don't know what I can/should do to make it appear in linux-next. Dave, unless you think there is a risk in applying this patch, could you take it in your drm-next tree ? Best Regards, Boris [1]http://www.spinics.net/lists/dri-devel/msg75848.html -- Boris Brezillon, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com