<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>2518</bug_id>
          
          <creation_ts>2012-05-29 18:16:20 +0000</creation_ts>
          <short_desc>linux-korg recipe does not work with v3.4 kernel</short_desc>
          <delta_ts>2012-06-12 15:55:45 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>6</classification_id>
          <classification>Yocto Project Subprojects</classification>
          <product>Kernel</product>
          <component>kernel-tooling</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>VERIFIED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Undecided</priority>
          <bug_severity>major</bug_severity>
          <target_milestone>1.3 M1</target_milestone>
          
          <blocked>2446</blocked>
          <everconfirmed>1</everconfirmed>
          <reporter name="Nitin Kamble">nitin.a.kamble</reporter>
          <assigned_to name="Bruce Ashfield">bruce.ashfield</assigned_to>
          <cc>bruce.ashfield</cc>
    
    <cc>dvhart</cc>
    
    <cc>laurentiu.serban</cc>
    
    <cc>yp.kernel.watcher</cc>
    
    <cc>yp.watcher</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>21704</commentid>
    <comment_count>0</comment_count>
    <who name="Nitin Kamble">nitin.a.kamble</who>
    <bug_when>2012-05-29 18:16:20 +0000</bug_when>
    <thetext>Error reported:

DEBUG: Executing shell function do_patch
ERROR: Function failed: do_patch (see /srv/home/nitin/builds/build-x32/tmp/work/qemux86_64-poky-linux-gnux32/linux-korg-3.4+git1+76e10d158efb6d4516018846f60c2ab5501900bc-r0/temp/log.do_patch.12214 for further information)
ERROR. meta data not found, check upstream repo for tags and branches


The recipe file: cat linux-korg_3.4.bb

inherit kernel
require recipes-kernel/linux/linux-yocto.inc

KMACHINE = &quot;x32&quot;
YOCTO_KERNEL_EXTERNAL_BRANCH = &quot;master&quot;
YOCTO_KERNEL_META_DATA = &quot;&quot;

KBRANCH = &quot;${KMACHINE}&quot;
KMETA = &quot;meta&quot;

SRC_URI = &quot;git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git;nocheckout=1;branch=master;bareclone=1 \
           file://defconfig \
           &quot;

SRCREV = &quot;76e10d158efb6d4516018846f60c2ab5501900bc&quot;

LINUX_VERSION = &quot;3.4&quot;
LOCALCOUNT = &quot;0&quot;
LINUX_VERSION_EXTENSION ?= &quot;-yoctized-${LINUX_KERNEL_TYPE}&quot;
PR = &quot;r0&quot;
PV = &quot;${LINUX_VERSION}+git${SRCPV}&quot;

#COMPATIBLE_MACHINE = &quot;(qemuarm|qemux86|qemuppc|qemumips|qemux86-64)&quot;

# Functionality flags
KERNEL_REVISION_CHECKING = &quot;&quot;

# extra tasks
addtask kernel_link_vmlinux after do_compile before do_install
addtask validate_branches before do_patch after do_kernel_checkout
addtask kernel_configcheck after do_configure before do_compile

#require recipes-kernel/linux/linux-tools.inc</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>21705</commentid>
    <comment_count>1</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2012-05-29 18:26:48 +0000</bug_when>
    <thetext>We&apos;ll be replacing linux-korg with linux-yocto-custom. It worked with
3.4 last I checked. I&apos;ll double check, since there are some pending
updates.

If you really want the 3.4 kernel, master branch, you&apos;d be better off
using linux-yocto-dev and shortly linux-yocto_3.4.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>21706</commentid>
    <comment_count>2</comment_count>
    <who name="Nitin Kamble">nitin.a.kamble</who>
    <bug_when>2012-05-29 19:37:54 +0000</bug_when>
    <thetext>Bruce,
   where is linux-yocto-dev recipe ? is it based on v3.4 ?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>21710</commentid>
    <comment_count>3</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2012-05-29 20:54:37 +0000</bug_when>
    <thetext>You should see:

http://git.yoctoproject.org/cgit/cgit.cgi/poky-extras/tree/meta-kernel-dev/recipes-kernel/linux/linux-yocto-dev.bb

In your poky-extras. The tree is based on 3.4 and will shortly be
renamed linux-yocto_3.4.bb .. but is completely usable at the moment,
since it is the basis for the next yocto kernel.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>21721</commentid>
    <comment_count>4</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2012-05-30 05:38:08 +0000</bug_when>
    <thetext>Are you working out of master ? You&apos;ll need to grab the latest 
example linux-korg example out of meta-kernel-dev in poky-extras and 
master of yocto-kernel-tools if you want linux-korg to work.

I have a pending review for the updates to kern tools, but ensure that
your SRCREV is set to 0859d2f73cc6f6973835fa5713b5a98a43ed43ff to get
all the fixes.

With that, and using the linux-korg reference in poky-extras, it will build.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>21756</commentid>
    <comment_count>5</comment_count>
    <who name="Nitin Kamble">nitin.a.kamble</who>
    <bug_when>2012-05-30 21:38:17 +0000</bug_when>
    <thetext>I was on master only. I looked at the linux-korg.bb from poky-extras. And I changed my linux-korg recipe similarly. And now it is working as expected.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>22044</commentid>
    <comment_count>6</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2012-06-12 13:00:35 +0000</bug_when>
    <thetext>Why are we changing the asignee for this bug ? Putting it back to myself.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>22048</commentid>
    <comment_count>7</comment_count>
    <who name="Laurentiu Serban">laurentiu.serban</who>
    <bug_when>2012-06-12 13:34:17 +0000</bug_when>
    <thetext>It was set to resolved fixed.
And the target milestone is 1.3M1
So it should be verified by someone...</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>22049</commentid>
    <comment_count>8</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2012-06-12 13:40:59 +0000</bug_when>
    <thetext>Aha. I can do the verification. But we don&apos;t need to change the assignee for the bug, just for verification .. do we ?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>22060</commentid>
    <comment_count>9</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2012-06-12 14:24:55 +0000</bug_when>
    <thetext>(In reply to comment #8)
&gt; Aha. I can do the verification. But we don&apos;t need to change the assignee for
&gt; the bug, just for verification .. do we ?

No, we do not need to change the assignee just to verify it, but if it is a long process to do the verification, it might make it easier for QA to track if it is assigned to them. I would try to use the RESOLVED state for the queries first and only reassign if that proves inadequate.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>22064</commentid>
    <comment_count>10</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2012-06-12 15:55:45 +0000</bug_when>
    <thetext>verified on 

meta-yocto        = &quot;master:cc96daa4443ca39e409040e3e4aff783658b8f6a&quot;
meta-kernel-dev   = &quot;master:86238cfede00c2fe5c43d6dcbf40c6f37748bac0&quot;

linux-korg + a valid defconfig patches and builds.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>