**** BEGIN LOGGING AT Thu Jun 18 02:59:59 2015 Jun 18 07:27:52 good morning Jun 18 08:36:15 hi mckoan Jun 18 08:39:37 hi woglinde Jun 18 09:53:02 morning all Jun 18 10:34:35 morning all Jun 18 10:34:57 hey Jun 18 11:38:54 whats the proper way to resolve patch failures for the kernel? do_patch fails, it tells me to run bitbake -c devshell to resolve it, but doing that just runs do_patch again (which fails..). It doesn't tell me which patch is the offending one (i have a lot of them) Jun 18 11:41:00 mago_: hmm, that's not very good is it ... Jun 18 11:41:10 in fact, it tells me this: Jun 18 11:41:19 | error: patch failed: include/linux/phy_fixed.h:14 Jun 18 11:41:22 | error: include/linux/phy_fixed.h: patch does not apply Jun 18 11:41:32 seems like its trying to apply a header file as a patch? Jun 18 11:41:41 but i only have .patch files in my SRC_URI Jun 18 11:42:07 I couldn't tell you what's going on there Jun 18 11:42:25 is this a linux-yocto style kernel? Jun 18 11:43:33 mago_: Does PATCHRESOLVE="user" work or is that something that does not work for the kernel recipes? Jun 18 11:43:57 it's the xilinx kernel.. it does include linux-yocto.inc, if that makes it a linux-yocto style kernel Jun 18 11:44:29 mago_: it does, yes Jun 18 11:44:42 you could try PATCHRESOLVE yes Jun 18 11:47:39 bluelightning: nrossi: PATCHRESOLVE="user" makes no difference it seems. Jun 18 11:48:28 I guess linux-yocto's custom patching process doesn't support that Jun 18 11:48:52 you could try pinging zeddii in #yocto Jun 18 14:21:11 bluelightning: that is a bit of an impressive failing for the patch resolver :( Jun 18 14:35:46 nrossi: i was able to get fixed phys working, i decided to stick with linux-xlnx 3.14 and backported the 3.16 fixed phy OF stuff and then made a patch for macb Jun 18 15:42:07 why does bitbake-whatchanged indicate tasks need to be run even when no changes have been made? When I actually build the recipe, nothing needs to run, but bitbake-whatchanged still prints that there are newly added tasks Jun 18 16:01:16 consmith: it's probably broken if that's what it's reporting Jun 18 16:03:31 bluelightning: that's unfortunate :( to clarify, I did a cleanall for the recipe, built it, and then immediately ran bitbake-whatchanged on it **** ENDING LOGGING AT Fri Jun 19 02:59:59 2015