On Fri, Dec 08, 2017 at 10:12:05PM +0100, Hans Verkuil wrote: ... > > I've applied all your patches. Thank you very much for working on this. > > Let's see what the result of the nightly build will be. > > In general reverting kernel patches to make a driver compile is something of a > last resort. It tends to be painful to maintain in the long run, at least, that's > been my experience. > Hi, thanks both for your work on this. Not quite there yet however. $ make allyesconfig make -C /home/me/git/clones/media_build/v4l allyesconfig make[1]: Entering directory '/home/me/git/clones/media_build/v4l' No version yet, using 4.4.0-103-generic make[2]: Entering directory '/home/me/git/clones/media_build/linux' Syncing with dir ../media/ Applying patches for kernel 4.4.0-103-generic patch -s -f -N -p1 -i ../backports/api_version.patch patch -s -f -N -p1 -i ../backports/pr_fmt.patch 1 out of 1 hunk FAILED Makefile:130: recipe for target 'apply_patches' failed make[2]: *** [apply_patches] Error 1 make[2]: Leaving directory '/home/me/git/clones/media_build/linux' Makefile:374: recipe for target 'allyesconfig' failed make[1]: *** [allyesconfig] Error 2 make[1]: Leaving directory '/home/me/git/clones/media_build/v4l' Makefile:26: recipe for target 'allyesconfig' failed make: *** [allyesconfig] Error 2 can't select all drivers at ./build line 525 + status=29 FWIW I also get the same failure on a 4.10 machine: + cat /proc/version_signature Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 I will have a look to see if I can spot this one. Cheers Vince
