On Mon, Aug 26, 2013 at 07:22:46PM +0000, Yang, Fei wrote: > >From 5e6501efa26bc19dad0b43e3a2b0daa81408a8ae Mon Sep 17 00:00:00 2001 > From: Fei Yang <fei.yang@xxxxxxxxx> > Date: Mon, 26 Aug 2013 11:21:48 -0700 > Subject: [PATCH] FIXDEP: error opening depfile > > Met a kernel build issue where fixdep fails to open a depfile, > fixdep: error opening depfile: drivers/driver-name/.driver-code.o.d: No such file or directory > make[4]: *** [drivers/driver-name/driver-code.o] Error 2 > make[3]: *** [drivers/driver-name] Error 2 > Don't know why the expected file was not created, but the assumption that > the file had been created might not be true, so simply return for such failure. I tried to grep: git grep "driver-name" No hits. Are you trying to fix a build issue with something out-of-tree - or is this only in linux-next? Sam -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
