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
