From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-oi0-f66.google.com ([209.85.218.66]:35346 "EHLO mail-oi0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751062AbdEaNe7 (ORCPT ); Wed, 31 May 2017 09:34:59 -0400 MIME-Version: 1.0 In-Reply-To: <20170531131216.GJ3956@linux.vnet.ibm.com> References: <20170530112027.3983554-1-arnd@arndb.de> <7b6903a2-ce54-44f9-18ed-a14bd32069ce@broadcom.com> <20170531131216.GJ3956@linux.vnet.ibm.com> From: Arnd Bergmann Date: Wed, 31 May 2017 15:34:57 +0200 Message-ID: (sfid-20170531_153522_568899_0D80E335) Subject: Re: [PATCH] bcm47xx: fix build regression To: "Paul E. McKenney" Cc: Arend van Spriel , =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= , Brian Norris , linux-mtd , linux-wireless , Linux Kernel Mailing List , "open list:RALINK MIPS ARCHITECTURE" , Ingo Molnar Content-Type: text/plain; charset="UTF-8" Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, May 31, 2017 at 3:12 PM, Paul E. McKenney wrote: > On Wed, May 31, 2017 at 12:21:10PM +0200, Arnd Bergmann wrote: >> On Wed, May 31, 2017 at 11:43 AM, Arend van Spriel >> wrote: >> > On 5/30/2017 1:20 PM, Arnd Bergmann wrote: >> >> >> >> An unknown change in the kernel headers caused a build regression >> >> in an MTD partition driver: >> >> >> >> In file included from drivers/mtd/bcm47xxpart.c:12:0: >> >> include/linux/bcm47xx_nvram.h: In function 'bcm47xx_nvram_init_from_mem': >> >> include/linux/bcm47xx_nvram.h:27:10: error: 'ENOTSUPP' undeclared (first >> >> use in this function) >> >> >> >> Clearly we want to include linux/errno.h here. >> > >> > >> > unfortunate that you did not find the commit that caused this build >> > regression. You could produce preprocessor output when it was working to see >> > where errno.h got implicitly included and start looking there for git >> > history. >> >> I did a 'git bisect run make drivers/mtd/bcm47xxpart.o' now, which pointed to >> 0bc2d534708b ("rcu: Refactor #includes from include/linux/rcupdate.h"). >> >> That commit seems reasonable, it was just bad luck that it caused this >> regression. The commit is currently in the rcu/rcu/next branch of tip.git, >> so Paul could merge the patch there. > > Apologies for the inconvenience, not sure why 0day test robot didn't > find this. Probably because it cannot test each and every driver. ;-) No worries. > This patch, correct? > > https://lkml.org/lkml/2017/5/30/348 Right, I should have included the link. Arnd