summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-09-12 16:23:03 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-09-22 12:20:42 +0100
commit6bf4106edda1e457a94ccf6b508127c1a6b36277 (patch)
tree77e2c38b5fff95e3afcc0a984059c65d86b812c2
parente3ed36e882745a7327041894a72a007bde1e6c0a (diff)
downloadpoky-6bf4106edda1e457a94ccf6b508127c1a6b36277.tar.gz
kernel-dev: Updated the in-tree metadata section
Fixes [YOCTO #5065] I added a blurb at the end of the section that talks about in-tree metadata. The blurb addresses situations where the user has changed the metadata but not updated the corresponding SRCREV variables in the kernel receipe. (From yocto-docs rev: 5d3dc0e6ebc40b937c3f3ef397e2c94e7cb3b69b) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/kernel-dev/kernel-dev-advanced.xml14
1 files changed, 14 insertions, 0 deletions
diff --git a/documentation/kernel-dev/kernel-dev-advanced.xml b/documentation/kernel-dev/kernel-dev-advanced.xml
index d15e26ffbf..4589e4b9fc 100644
--- a/documentation/kernel-dev/kernel-dev-advanced.xml
+++ b/documentation/kernel-dev/kernel-dev-advanced.xml
@@ -296,6 +296,20 @@
296 $ git commit --allow-empty -m "Create orphan meta branch" 296 $ git commit --allow-empty -m "Create orphan meta branch"
297 </literallayout> 297 </literallayout>
298 </para> 298 </para>
299
300 <para>
301 If you modify the Metadata in the linux-yocto
302 <filename>meta</filename> branch, you must not forget to update
303 the
304 <ulink url='&YOCTO_DOCS_REF_URL;#var-SRCREV'><filename>SRCREV</filename></ulink>
305 statements in the kernel's recipe.
306 In particular, you need to update the
307 <filename>SRCREV_meta</filename> variable to match the commit in
308 the <filename>KMETA</filename> branch you wish to use.
309 Changing the data in these branches and not updating the
310 <filename>SRCREV</filename> statements to match will cause the
311 build to fetch an older commit.
312 </para>
299 </section> 313 </section>
300</section> 314</section>
301 315