From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752904AbbCaXH4 (ORCPT ); Tue, 31 Mar 2015 19:07:56 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:54868 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752786AbbCaXHy (ORCPT ); Tue, 31 Mar 2015 19:07:54 -0400 Date: Wed, 1 Apr 2015 01:07:49 +0200 From: Greg Kroah-Hartman To: Guenter Roeck Cc: Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Tony Lindgren , Felipe Balbi , Ard Biesheuvel , Russell King , Arnd Bergmann , Lad@roeck-us.net, Prabhakar , Thomas Gleixner , Daniel Mack , Mikko Perttunen , Thierry Reding Subject: Re: linux-next: Tree for Mar 31 (build failures and culprits) Message-ID: <20150331230749.GA6564@kroah.com> References: <20150401000221.21961ecd@canb.auug.org.au> <20150331161640.GA16540@roeck-us.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20150331161640.GA16540@roeck-us.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 31, 2015 at 09:16:40AM -0700, Guenter Roeck wrote: > On Wed, Apr 01, 2015 at 12:02:21AM +1100, Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20150330: > > > > The arm64 tree gained a conflict against the arm-soc tree. > > > > The idle tree gained a build failure so I used the version from > > next-20150327. > > > > The tip tree gained conflicts against the pm tree. > > > > The akpm tree gained a conflict against the mips tree. > > > > Non-merge commits (relative to Linus' tree): 7277 > > 6623 files changed, 304342 insertions(+), 138111 deletions(-) > > > > ---------------------------------------------------------------------------- > > > > Build results: > total: 121 pass: 94 fail: 27 > Failed builds: > alpha:allmodconfig > arm:rpc_defconfig > arm64:defconfig > cris:defconfig > cris:etrax-100lx_defconfig > cris:allnoconfig > frv:defconfig > i386:allyesconfig > i386:allmodconfig > ia64:defconfig > m32r:defconfig > m68k:defconfig > m68k:allmodconfig > m68k:sun3_defconfig > m68k:m5272c3_defconfig > m68k:m5307c3_defconfig > m68k:m5249evb_defconfig > m68k:m5407c3_defconfig > m68k:m5475evb_defconfig > mips:allmodconfig > parisc:defconfig > parisc:generic-32bit_defconfig > parisc:a500_defconfig > parisc:generic-64bit_defconfig > x86_64:allyesconfig > xtensa:defconfig > xtensa:allmodconfig > > --- > alpha:allmodconfig > mips:allmodconfig > > samples/kdbus/kdbus-workers.c: In function ‘prime_new’: > samples/kdbus/kdbus-workers.c:930:18: error: ‘__NR_memfd_create’ undeclared > (first use in this function) > p->fd = syscall(__NR_memfd_create, "prime-area", MFD_CLOEXEC); > > Looks like the kdbus example never worked for the affected architectures. > I don't build allmodconfig for all architectures, so other architectures > may be affected as well. You need 3.17 kernel headers to have memfd_create, not much the kdbus test code can do about that. You might want to update the kernel headers for these build boxes. Or have we not hooked up memfd for alpha and mips? thanks, greg k-h