diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2013-04-16 14:18:41 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-04-17 22:34:19 +0100 |
commit | 9bf1cde472bb638a68dbf1a9c37252cbb736df90 (patch) | |
tree | 7cf7a1a763960357ebfdcc369b2d1a2d8fd3741f /documentation/kernel-dev/kernel-dev-advanced.xml | |
parent | 6668012b673b6e2cffb46e27a267f2b02ef57eca (diff) | |
download | openembedded-core-contrib-9bf1cde472bb638a68dbf1a9c37252cbb736df90.tar.gz |
kernel-dev: Eliminated a redundant paragraph.
Noticed the exact same paragraph at the beginning of Chapter 3
that also appears in the introductory text for the manual.
(From yocto-docs rev: 431cb58ca144bbf5aa49caa7dc2b728c3c92fe66)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/kernel-dev/kernel-dev-advanced.xml')
-rw-r--r-- | documentation/kernel-dev/kernel-dev-advanced.xml | 20 |
1 files changed, 0 insertions, 20 deletions
diff --git a/documentation/kernel-dev/kernel-dev-advanced.xml b/documentation/kernel-dev/kernel-dev-advanced.xml index ba288d1311..c9612c9527 100644 --- a/documentation/kernel-dev/kernel-dev-advanced.xml +++ b/documentation/kernel-dev/kernel-dev-advanced.xml @@ -18,26 +18,6 @@ to help you manage the complexity of the configuration and sources used to support multiple BSPs and Linux kernel types. </para> - - <para> - In particular, the kernel tools allow you to specify only what you - must, and nothing more. - Where a complete Linux kernel <filename>.config</filename> includes - all the automatically selected <filename>CONFIG</filename> options, - the configuration fragments only need to contain the highest level - visible <filename>CONFIG</filename> options as presented by the Linux - kernel <filename>menuconfig</filename> system. - This reduces your maintenance effort and allows you - to further separate your configuration in ways that make sense for - your project. - A common split is policy and hardware. - For example, all your kernels might support - the <filename>proc</filename> and <filename>sys</filename> filesystems, - but only specific boards will require sound, USB, or specific drivers. - Specifying these individually allows you to aggregate them - together as needed, but maintain them in only one place. - Similar logic applies to source changes. - </para> </section> <section id='using-kernel-metadata-in-a-recipe'> |