From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: linux-next: build failure after merge of the staging tree Date: Tue, 7 Mar 2017 05:46:43 +0100 Message-ID: <20170307044643.GA3684@kroah.com> References: <20170307122542.49126980@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from out4-smtp.messagingengine.com ([66.111.4.28]:55489 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751773AbdCGFb3 (ORCPT ); Tue, 7 Mar 2017 00:31:29 -0500 Content-Disposition: inline In-Reply-To: <20170307122542.49126980@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Alan Cox On Tue, Mar 07, 2017 at 12:25:42PM +1100, Stephen Rothwell wrote: > Hi Greg, > > After merging the staging tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/staging/media/atomisp/i2c/mt9m114.c:38:41: fatal error: linux/atomisp_gmin_platform.h: No such file or directory > drivers/staging/media/atomisp/i2c/gc2235.c:32:41: fatal error: linux/atomisp_gmin_platform.h: No such file or directory > drivers/staging/media/atomisp/i2c/ov2722.c:32:41: fatal error: linux/atomisp_gmin_platform.h: No such file or directory > drivers/staging/media/atomisp/platform/clock/vlv2_plat_clock.c:25:35: fatal error: linux/vlv2_plat_clock.h: No such file or directory > drivers/staging/media/atomisp/platform/intel-mid/intel_mid_pcihelpers.c:28:38: fatal error: asm/intel_mid_pcihelpers.h: No such file or directory > drivers/staging/media/atomisp/platform/intel-mid/atomisp_gmin_platform.c:10:35: fatal error: linux/vlv2_plat_clock.h: No such file or directory > In file included from drivers/staging/media/atomisp/pci/atomisp2/./atomisp_drvfs.c:26:0: > drivers/staging/media/atomisp/pci/atomisp2/./atomisp_compat.h:27:27: fatal error: linux/atomisp.h: No such file or directory > > Caused by commit > > a49d25364dfb ("staging/atomisp: Add support for the Intel IPU v2") > > or maybe some of the followups? > > I have used the staging tree from next-20170306 for today. I just got a report from the kbuild bot about this as well, it didn't used to happen before, and I can't duplicate it myself. Alan, any hints as to what broke here? thanks, greg k-h