summaryrefslogtreecommitdiffstats
path: root/documentation/kernel-manual/kernel-how-to.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/kernel-manual/kernel-how-to.xml')
-rw-r--r--documentation/kernel-manual/kernel-how-to.xml20
1 files changed, 11 insertions, 9 deletions
diff --git a/documentation/kernel-manual/kernel-how-to.xml b/documentation/kernel-manual/kernel-how-to.xml
index 756758d8a3..125212b986 100644
--- a/documentation/kernel-manual/kernel-how-to.xml
+++ b/documentation/kernel-manual/kernel-how-to.xml
@@ -10,8 +10,8 @@
10 <title>Introduction</title> 10 <title>Introduction</title>
11 <para> 11 <para>
12 This chapter describes how to accomplish tasks involving the kernel's tree structure. 12 This chapter describes how to accomplish tasks involving the kernel's tree structure.
13 This information is designed to help the developer that wants to modify the Yocto Project kernel 13 The information is designed to help the developer that wants to modify the Yocto
14 and contribute changes upstream to the Yocto Project. 14 Project kernel and contribute changes upstream to the Yocto Project.
15 The information covers the following: 15 The information covers the following:
16 <itemizedlist> 16 <itemizedlist>
17 <listitem><para>Tree construction</para></listitem> 17 <listitem><para>Tree construction</para></listitem>
@@ -24,10 +24,11 @@
24 <section id='tree-construction'> 24 <section id='tree-construction'>
25 <title>Tree Construction</title> 25 <title>Tree Construction</title>
26 <para> 26 <para>
27 This section describes construction of the Yocto Project kernel repositories as accomplished 27 This section describes construction of the Yocto Project kernel repositories
28 by the Yocto Project team to create kernel repositories, which are found at 28 as accomplished by the Yocto Project team to create kernel repositories.
29 <ulink url='http://git.yoctoproject.org/cgit.cgi'>http://git.yoctoproject.org/cgit.cgi</ulink>, 29 These kernel repositories are found at
30 that can be shipped as part of a Yocto Project release. 30 <ulink url='http://git.yoctoproject.org/cgit.cgi'>http://git.yoctoproject.org/cgit.cgi</ulink>
31 and can be shipped as part of a Yocto Project release.
31 The team creates these repositories by 32 The team creates these repositories by
32 compiling and executing the set of feature descriptions for every BSP/feature 33 compiling and executing the set of feature descriptions for every BSP/feature
33 in the product. 34 in the product.
@@ -129,7 +130,8 @@
129 <ulink url='http://git.yoctoproject.org/cgit.cgi'>http://git.yoctoproject.org/cgit.cgi</ulink> 130 <ulink url='http://git.yoctoproject.org/cgit.cgi'>http://git.yoctoproject.org/cgit.cgi</ulink>
130 is the combination of all supported boards and configurations.</para> 131 is the combination of all supported boards and configurations.</para>
131 <para>The technique the Yocto Project team uses is flexible and allows for seamless 132 <para>The technique the Yocto Project team uses is flexible and allows for seamless
132 blending of an immutable history with additional deployment specific patches. 133 blending of an immutable history with additional patches specific to a
134 deployment.
133 Any additions to the kernel become an integrated part of the branches.</para> 135 Any additions to the kernel become an integrated part of the branches.</para>
134 </note> 136 </note>
135 </para> 137 </para>
@@ -263,9 +265,9 @@
263 265
264 <para> 266 <para>
265 Following are a few examples that show how to use Git to examine changes. 267 Following are a few examples that show how to use Git to examine changes.
266 Note that because the Yocto Project Git repository does not break existing Git 268 Because the Yocto Project Git repository does not break existing Git
267 functionality and because there exists many permutations of these types of 269 functionality and because there exists many permutations of these types of
268 commands there are many more methods to discover changes. 270 commands, there are many more methods to discover changes.
269 <note> 271 <note>
270 Unless you provide a commit range 272 Unless you provide a commit range
271 (&lt;kernel-type&gt;..&lt;bsp&gt;-&lt;kernel-type&gt;), <filename>kernel.org</filename> history 273 (&lt;kernel-type&gt;..&lt;bsp&gt;-&lt;kernel-type&gt;), <filename>kernel.org</filename> history