From patchwork Mon Dec 3 20:49:06 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [3/3] linux-yocto/3.4: inform the fetcher if the meta branch changes Date: Mon, 03 Dec 2012 20:49:06 -0000 From: Bruce Ashfield X-Patchwork-Id: 40087 Message-Id: To: richard.purdie@linuxfoundation.org Cc: openembedded-core@lists.openembedded.org The meta data branch for the kernel can be varied by changing the KMETA variable, but that change wasn't reflected in the SRC_URI, which means that the fetcher won't check for changes on that branch and is a potential source of errors. Making the meta branch specification KMETA vs meta solves the problem. Signed-off-by: Bruce Ashfield --- meta/recipes-kernel/linux/linux-yocto_3.4.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-kernel/linux/linux-yocto_3.4.bb b/meta/recipes-kernel/linux/linux-yocto_3.4.bb index 0e795c6..91785f9 100644 --- a/meta/recipes-kernel/linux/linux-yocto_3.4.bb +++ b/meta/recipes-kernel/linux/linux-yocto_3.4.bb @@ -11,7 +11,7 @@ SRCREV_machine_qemux86-64 ?= "b13bef6377719a488293af196236cc290566fad3" SRCREV_machine ?= "b13bef6377719a488293af196236cc290566fad3" SRCREV_meta ?= "6737e890fff2a423fbb022ab1f7f82ef187fd8b1" -SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.4.git;protocol=git;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta" +SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.4.git;protocol=git;nocheckout=1;branch=${KBRANCH},${KMETA};name=machine,meta" LINUX_VERSION ?= "3.4.20"