<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openembedded-core.git/meta/recipes-kernel/linux/linux-yocto_2.6.34.bb, branch 2011-1</title>
<subtitle>Mirror of openembedded-core</subtitle>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/openembedded-core.git/'/>
<entry>
<title>kernel.bbclass: Add support for perf-dbg package</title>
<updated>2011-06-23T11:05:11+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@windriver.com</email>
</author>
<published>2011-06-20T17:58:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/openembedded-core.git/commit/?id=17f76de8ab8b7c9e62c1149017a3fa78866d9300'/>
<id>17f76de8ab8b7c9e62c1149017a3fa78866d9300</id>
<content type='text'>
The perf component is built with the kernel, so ensure that it gets the
debug information associated with it.

Also bump the PR in the linux-yocto-* to ensure they get rebuilt.

Signed-off-by: Mark Hatle &lt;mark.hatle@windriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The perf component is built with the kernel, so ensure that it gets the
debug information associated with it.

Also bump the PR in the linux-yocto-* to ensure they get rebuilt.

Signed-off-by: Mark Hatle &lt;mark.hatle@windriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>linux-yocto: rename recipes to explicitly indicate version</title>
<updated>2011-06-14T12:15:52+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@windriver.com</email>
</author>
<published>2011-06-08T19:33:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/openembedded-core.git/commit/?id=576c87349a72a94357014ff29f55db692903ed80'/>
<id>576c87349a72a94357014ff29f55db692903ed80</id>
<content type='text'>
The existing recipe names for the linux-yocto kernel builds
worked well when there was a single, or two versions of the
kernel available. But with the impending kernel updates and
retirement of older kernels, the re-use of the same recipes
for different kernel versions violates the principle of least
surprise.

To address this, the recipes are being renamed as follows:

    linux-yocto_git.bb -&gt; linux-yocto_2.6.37.bb
    linux-yocto-stable_git.bb -&gt; linux-yocto_2.6.34.bb

There continue to be versionless recipe names that feed into
versioned recipes at the appropriate points. They are:

     linux-yocto-dev.bb (tracking the latest yocto dev kernel)
     linux-yocto-korg_head.bb (tracking korg kernels)

There are no existing users of linux-yocto-stable in the master
branches to convert to the new naming, so these changes work
in isolation.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The existing recipe names for the linux-yocto kernel builds
worked well when there was a single, or two versions of the
kernel available. But with the impending kernel updates and
retirement of older kernels, the re-use of the same recipes
for different kernel versions violates the principle of least
surprise.

To address this, the recipes are being renamed as follows:

    linux-yocto_git.bb -&gt; linux-yocto_2.6.37.bb
    linux-yocto-stable_git.bb -&gt; linux-yocto_2.6.34.bb

There continue to be versionless recipe names that feed into
versioned recipes at the appropriate points. They are:

     linux-yocto-dev.bb (tracking the latest yocto dev kernel)
     linux-yocto-korg_head.bb (tracking korg kernels)

There are no existing users of linux-yocto-stable in the master
branches to convert to the new naming, so these changes work
in isolation.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
</pre>
</div>
</content>
</entry>
</feed>
