diff options
Diffstat (limited to 'documentation/kernel-dev/concepts-appx.rst')
| -rw-r--r-- | documentation/kernel-dev/concepts-appx.rst | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/documentation/kernel-dev/concepts-appx.rst b/documentation/kernel-dev/concepts-appx.rst index cf2e75d853..6a2fe4bb0b 100644 --- a/documentation/kernel-dev/concepts-appx.rst +++ b/documentation/kernel-dev/concepts-appx.rst @@ -117,7 +117,7 @@ upstream Linux kernel development and are managed by the Yocto Project team's Yocto Linux kernel development strategy. It is the Yocto Project team's policy to not back-port minor features to the released Yocto Linux kernel. They only consider back-porting significant technological -jumps - and, that is done after a complete gap analysis. The reason +jumps --- and, that is done after a complete gap analysis. The reason for this policy is that back-porting any small to medium sized change from an evolving Linux kernel can easily create mismatches, incompatibilities and very subtle errors. @@ -211,8 +211,8 @@ view, there is a linear path that travels from the baseline ``kernel.org``, through a select group of features and ends with their BSP-specific commits. In other words, the divisions of the kernel are transparent and are not relevant to the developer on a day-to-day basis. -From the developer's perspective, this path is the "master" branch in -Git terms. The developer does not need to be aware of the existence of +From the developer's perspective, this path is the development branch. +The developer does not need to be aware of the existence of any other branches at all. Of course, it can make sense to have these branches in the tree, should a person decide to explore them. For example, a comparison between two BSPs at either the commit level or at @@ -221,7 +221,7 @@ the line-by-line code ``diff`` level is now a trivial operation. The following illustration shows the conceptual Yocto Linux kernel. .. image:: figures/kernel-architecture-overview.png - :align: center + :width: 100% In the illustration, the "Kernel.org Branch Point" marks the specific spot (or Linux kernel release) from which the Yocto Linux kernel is @@ -318,12 +318,12 @@ tree specific to your kernel from which to generate the new kernel image. The following figure shows the temporary file structure created on your -host system when you build the kernel using Bitbake. This -:term:`Build Directory` contains all the -source files used during the build. +host system when you build the kernel using BitBake. This +:term:`Build Directory` contains all the source files used during the build. .. image:: figures/kernel-overview-2-generic.png :align: center + :width: 70% Again, for additional information on the Yocto Project kernel's architecture and its branching strategy, see the |