After modifying the meta-data in the linux-yocto meta branch, a kernel developer should not forget to update the SRCREVs in the linux-yocto_3.8.bb recipe. This should be explicitly mentioned int the kernel development manual, else a kernel developer, new to modifying and updating the linux-yocto kernel meta data might spend hours or days trying to figure out why changes haven't been picked up by the build system.
I'm thinking a blurb could be added to "3.3.2. In-Tree Metadata" in the kernel-dev manual about being sure to update the SRCREV_meta variable to match the commit in the KMETA branch you wish to use. The question is, would that have avoided the problem for you? I want to understand which sections you read and why you read them first. Was this one of them? If not, which one did you read? Would one of them need an update, or is some other higher level introduction to the SRCREV* vars needed elsewhere in the document?
Darren, When you get more clarification on this we can update the manual. I'm on the CC list so will be able to track it. Scott
Scott, what clarification do you need? As far as the manual is concerned, whenever changes are made to any of the branches with associated SRCREV, typically: SRCREV_machine (something like standard/minnowboard, but defined by KBRANCH) SRCREV_meta (typically just meta, but defined by KMETA) If you change these branches and want to rebuild from the source using the recipe, you need to update the corresponding SRCREV to match or you will be fetching an older commit.
Reassigning to Scott with information provided. Scott, please let me know if that is enough to get changes in. If you would prefer I update the manual directly we can do that as well.
Hi, I have added a paragraph at the end of the suggested section. Here is the link. http://www.yoctoproject.org/docs/1.5/kernel-dev/kernel-dev.html#in-tree-metadata It is very general and assumes people reading it know what they are doing. If you have comments or suggestions, add some comments here in Bugzilla. Scott
Hi Scott, The updated section looks fine. Elvis Dowson
Elvis, Thanks for the review. I am marking this bug resolved and turning off the Doc flag. Scott