Bug 597 - kernel manual: preempt_rt now named preempt-rt
Summary: kernel manual: preempt_rt now named preempt-rt
Status: VERIFIED FIXED
Alias: None
Product: Reference
Classification: Documentation
Component: handbook (show other bugs)
Version: 1.0
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.0 M1
Assignee: Scott Rifenbark
QA Contact:
URL:
Whiteboard: 22 July 2011 - Verified
Depends on:
Blocks:
 
Reported: 2010-12-14 19:25 UTC by Darren Hart
Modified: 2011-07-22 07:39 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Darren Hart 2010-12-14 19:25:36 UTC
It was necessary to remove the "_" from the preempt_rt kernel type, which is now named preempt_rt. The documentation in the kernel manual as well as the kernel branching figure need to be updated to reflect that.
Comment 1 Bruce Ashfield 2010-12-15 08:15:53 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.
Comment 2 Scott Rifenbark 2011-02-01 09:33:47 UTC
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"
Comment 3 Bruce Ashfield 2011-02-01 10:30:06 UTC
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.
Comment 4 Scott Rifenbark 2011-02-08 09:32:15 UTC
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.
Comment 6 Scott Rifenbark 2011-07-22 07:39:12 UTC
Fixes in manuals