All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: yocto@yoctoproject.org
Subject: [meta-intel/danny][PATCH] meta-crystalforest, linux-yocto_3.4.bbappend: Pin LINUX_VERSION
Date: Tue, 23 Oct 2012 20:56:54 -0700	[thread overview]
Message-ID: <1351051014-15859-1-git-send-email-raj.khem@gmail.com> (raw)

meta-crystalforest BSPs uses 3.4.9 kernel but the default
yocto kernel is 3.4.11, if we do not pin the LINUX_VERSION
then we get inconsistent version number for bzImage and the modules
where modules are installed under /lib/modules/3.4.9-yocto-standard/
but kernel is called
bzImage-3.4.11+git2+9e3bdb7344054264b750e53fbbb6394cc1c942ac_1+0985844fa6235422c67ef269952fa4e765f252f9-r4.3-crystalforest-stargo-20121024031021.bin

This patch fixes this mismatch. Beaware that other BSPs from
meta-intel may need something similar too.

Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
 .../recipes-kernel/linux/linux-yocto_3.4.bbappend  |    3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta-crystalforest/recipes-kernel/linux/linux-yocto_3.4.bbappend b/meta-crystalforest/recipes-kernel/linux/linux-yocto_3.4.bbappend
index 082fe38..92aaa61 100644
--- a/meta-crystalforest/recipes-kernel/linux/linux-yocto_3.4.bbappend
+++ b/meta-crystalforest/recipes-kernel/linux/linux-yocto_3.4.bbappend
@@ -15,3 +15,6 @@ SRCREV_machine_pn-linux-yocto_crystalforest-shumway ?= "0985844fa6235422c67ef269
 SRCREV_meta_pn-linux-yocto_crystalforest-shumway ?= "9e3bdb7344054264b750e53fbbb6394cc1c942ac"
 
 module_autoload_uio = "uio"
+
+LINUX_VERSION = "3.4.9"
+
-- 
1.7.9.5



             reply	other threads:[~2012-10-24  3:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24  3:56 Khem Raj [this message]
2012-10-25 14:50 ` [meta-intel/danny][PATCH] meta-crystalforest, linux-yocto_3.4.bbappend: Pin LINUX_VERSION Tom Zanussi
  -- strict thread matches above, loose matches on Subject: below --
2012-10-25 15:36 Khem Raj
2012-10-25 21:50 ` Tom Zanussi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1351051014-15859-1-git-send-email-raj.khem@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.