When trying to use the older commit for the kernel branch like this: diff --git a/meta-emenlow/recipes-kernel/linux/linux-yocto_3.10.bbappend b/meta-emenlow/recipes-kernel/linux/linux-yocto_3.10.bbappend -LINUX_VERSION = "3.10.33" +LINUX_VERSION = "3.10.25" SRCREV_meta_emenlow = "99c503a92885060bebf2bba6747735e8e9346a40" -SRCREV_machine_emenlow = "21df0c8486e129a4087970a07b423c533ae05de7" +SRCREV_machine_emenlow = "79af968f2f26378798aec7a6d729ff5a371aae5f" SRCREV_emgd_emenlow = "42d5e4548e8e79e094fa8697949eed4cf6af00a3" SRCREV_meta_emenlow-noemgd = "6e0e756d51372c8b176c5d1e6f786545bceed351" -SRCREV_machine_emenlow-noemgd = "21df0c8486e129a4087970a07b423c533ae05de7" +SRCREV_machine_emenlow-noemgd = "79af968f2f26378798aec7a6d729ff5a371aae5f" the kernel is still build with the latest HEAD: > pwd .../build/tmp/work/emenlow_noemgd-poky-linux/linux-yocto/3.10.25+gitAUTOINC+6e0e756d51_79af968f2f-r0/linux > head Makefile VERSION = 3 PATCHLEVEL = 10 SUBLEVEL = 33 EXTRAVERSION = -ltsi > git log commit 21df0c8486e129a4087970a07b423c533ae05de7 Merge: 78afd30 6969595 Author: Bruce Ashfield <bruce.ashfield@windriver.com> Date: Thu Mar 13 14:05:29 2014 -0400 Merge tag 'v3.10.33' into standard/ltsi This is the 3.10.33 stable release Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Conflicts: Makefile commit 6969595f011b46b49c3f1b9e0bd7da27768c1fd9 Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Date: Thu Mar 6 21:58:45 2014 -0800 Linux 3.10.33 ... Expected result: the kernel is built with the specified commit.
This works perfectly here. Are you running with my test queue ? If so, don't use it, since it doesn't support this yet. If I set: SRCREV_machine_${MACHINE}="41235e1176a22251ac22581f2c0632407584d48b" for qemux86, and the head of standard/common-pc/base is really 78d2a615b13a1c307d482eaa9499c1b2dee40599 After the kernel patches and configures, the head of my tree is the SRCREV I specified, not the one at the head of the branch.
Thanks for the quick response Bruce. Yes I was using your test commits. After removing them the issue is gone.
seems that this works now.