path: root/meta-yocto/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
diff options
authorBruce Ashfield <>2012-06-07 19:59:50 (GMT)
committerRichard Purdie <>2012-06-08 10:56:32 (GMT)
commit27c051f00697181a43be5d9d755642e6e1bfec64 (patch)
treed23508d9ca9cfb86d6bd06159be77bdcc054d01b /meta-yocto/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
parent7f44713308fcb14a644932ae886ea6ccf88e88f3 (diff)
kern-tools: anchor KMACHINE test
Updating the kern-tools SRCREV to pick up the following fix: Out of tree feature descriptions (.scc files) take two forms: normal features and BSP descriptions. A normal feature is detected and added to the end of the current machine being processed. During tree processing, it's configuration and patches will be applied. A BSP description on the other hand must be matched based on three critera (which are in the .scc file via "define <foo>"): - machine - kernel type - architecture Since features that define machines are only explicitly added, they are removed from the list of features that should be automatically added. The criteria for removing them from the auto-add list is the definitions found in the .scc file. The existing check was simply for KMACHINE anywhere in the file. This meant that a conditional or even a comment containing that phrase would exclude a file. Properly anchoring the KMACHINE test to "^define.*KMACHINE" fixes the problem of overly agreesive exclusions. (From OE-Core rev: 75a973328d50ef3c007edb7a471ea77fb97911ea) Signed-off-by: Bruce Ashfield <> Signed-off-by: Richard Purdie <>
Diffstat (limited to 'meta-yocto/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend')
0 files changed, 0 insertions, 0 deletions