From ba33c69b24f38996e76656637d390df3b65084e7 Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <srifenbark@gmail.com>
Date: Thu, 5 Oct 2017 07:44:12 -0700
Subject: kernel-dev: Updated Tree Construction section with review feedback.

(From yocto-docs rev: c28b349a972d81d3b60bf1b0de48d837fbc76cdb)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 documentation/kernel-dev/kernel-dev-maint-appx.xml | 65 +++++++++++++++-------
 1 file changed, 44 insertions(+), 21 deletions(-)

diff --git a/documentation/kernel-dev/kernel-dev-maint-appx.xml b/documentation/kernel-dev/kernel-dev-maint-appx.xml
index 79e6e26e00..f5fd183fd0 100644
--- a/documentation/kernel-dev/kernel-dev-maint-appx.xml
+++ b/documentation/kernel-dev/kernel-dev-maint-appx.xml
@@ -154,8 +154,8 @@
                     </literallayout>
                 </para></listitem>
                 <listitem><para>
-                    <emphasis>Compile Feature:</emphasis>
-                    Once located, the feature description is either compiled
+                    <emphasis>Expand Feature:</emphasis>
+                    Once located, the feature description is either expanded
                     into a simple script of actions, or into an existing
                     equivalent script that is already part of the shipped
                     kernel.
@@ -169,8 +169,8 @@
                     variable in recipes.
                     </para></listitem>
                 <listitem><para>
-                    <emphasis>Locate, Compile, and Append Each Feature:</emphasis>
-                    Each extra feature is located, compiled and appended to
+                    <emphasis>Locate, Expand, and Append Each Feature:</emphasis>
+                    Each extra feature is located, expanded and appended to
                     the script as described in step three.
                     </para></listitem>
                 <listitem><para>
@@ -203,23 +203,46 @@
             The kernel tree and cache are ready for developer consumption to
             be locally cloned, configured, and built into a Yocto Project
             kernel specific to some target hardware.
-            <note>
-                <para>The generated <filename>yocto-kernel-cache</filename>
-                repository adds to the kernel as shipped with the Yocto Project
-                release.
-                Any add-ons and configuration data are applied to the end of
-                an existing branch.
-                The full repository generation that is found in the
-                official Yocto Project kernel repositories at
-                <ulink url='&YOCTO_GIT_URL;/cgit.cgi'>http://git.yoctoproject.org/cgit.cgi</ulink>
-                is the combination of all supported boards and configurations.
-                </para>
-
-                <para>The technique the Yocto Project team uses is flexible
-                and allows for seamless blending of an immutable history with
-                additional patches specific to a deployment.
-                Any additions to the kernel become an integrated part of the
-                branches.</para>
+            <note><title>Notes</title>
+                <itemizedlist>
+                    <listitem><para>
+                        The generated <filename>yocto-kernel-cache</filename>
+                        repository adds to the kernel as shipped with the Yocto
+                        Project release.
+                        Any add-ons and configuration data are applied to the
+                        end of an existing branch.
+                        The full repository generation that is found in the
+                        official Yocto Project kernel repositories at
+                        <ulink url='&YOCTO_GIT_URL;/cgit.cgi'>http://git.yoctoproject.org/cgit.cgi</ulink>
+                        is the combination of all supported boards and
+                        configurations.
+                        </para></listitem>
+                    <listitem><para>
+                        The technique the Yocto Project team uses is flexible
+                        and allows for seamless blending of an immutable
+                        history with additional patches specific to a
+                        deployment.
+                        Any additions to the kernel become an integrated part
+                        of the branches.
+                        </para></listitem>
+                    <listitem><para>
+                        The full kernel tree that you see on
+                        <ulink url='&YOCTO_GIT_URL;/cgit.cgi'></ulink> is
+                        generated through repeating the above steps for all
+                        valid BSPs.
+                        The end result is a branched, clean history tree that
+                        makes up the kernel for a given release.
+                        You can see the script (<filename>kgit-scc</filename>)
+                        responsible for this in the
+                        <ulink url='&YOCTO_GIT_URL;/cgit.cgi/yocto-kernel-tools/tree/tools'><filename>yocto-kernel-tools</filename></ulink>
+                        repository.
+                        </para></listitem>
+                    <listitem><para>
+                        The steps used to construct the full kernel tree are
+                        the same steps that BitBake uses when it builds a
+                        kernel image.
+                        </para></listitem>
+                </itemizedlist>
             </note>
         </para>
     </section>
-- 
cgit v1.2.3-54-g00ecf