| Summary: | kernel manual: preempt_rt now named preempt-rt | ||
|---|---|---|---|
| Product: | [Documentation] Reference | Reporter: | Darren Hart <dvhart> |
| Component: | handbook | Assignee: | Scott Rifenbark <srifenbark> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | bruce.ashfield, ke.yu, poky.doc.watcher, poky.watcher, richard.purdie, sgw |
| Version: | 1.0 | ||
| Target Milestone: | 1.0 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | 22 July 2011 - Verified | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Darren Hart
2010-12-14 19:25:36 UTC
There will be two slightly different fixes for this: 0.9: the preempt_rt kernel type will be translated to preempt-rt for the purposes of the Linux extension, which is used during packaging. Everything else stays the same. 1.0 aka 2.6.37: all branches have been renamed to not have any _ instances. So the branching in the docs needs to be updated for this. For version 1.0 does this mean that every instance of "_" in a pathname in the manual will be turned into a dash character? For example "linux-yocto_git.bbappend" Not all _ become -, only the ones that were referencing branch names in the kernel tree itself. common_pc-standard is common-pc-standard preempt_rt is preempt-rt etc. If there are any grey areas, point them out and I can help with the assessment. I have made changes to the manual changing "common_pc" to "common-pc". There are other strings in question. Email has been sent to Bruce Ashfield asking for clarification. Once I have that information I will close out the fix. Fixes in manuals |