From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755084AbdCGIuF (ORCPT ); Tue, 7 Mar 2017 03:50:05 -0500 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:47786 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754750AbdCGItQ (ORCPT ); Tue, 7 Mar 2017 03:49:16 -0500 X-ME-Sender: X-Sasl-enc: tC0WXUx0Zj983XcCxhcaWScrEiQ7VaUlHQWAnmmfV1o3 1488876454 Date: Tue, 7 Mar 2017 09:47:29 +0100 From: Greg KH To: Stephen Rothwell Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Alan Cox Subject: Re: linux-next: build failure after merge of the staging tree Message-ID: <20170307084729.GB20446@kroah.com> References: <20170307122542.49126980@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170307122542.49126980@canb.auug.org.au> User-Agent: Mutt/1.8.0 (2017-02-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 I really can't duplicate this here, but you and the kbuild bot are hitting this now. in drivers/staging/media/atomisp/Makefile we have: LINUXINCLUDE += -I drivers/staging/media/atomisp/include/ to point the include path at where atomisp_gmin_platform.h is at. So I don't understand what is going on here. Alan, any hints? thanks, greg k-h