summaryrefslogtreecommitdiffstats
path: root/documentation/kernel-dev
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-04-16 21:18:41 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-17 21:34:19 (GMT)
commit9bf1cde472bb638a68dbf1a9c37252cbb736df90 (patch)
tree7cf7a1a763960357ebfdcc369b2d1a2d8fd3741f /documentation/kernel-dev
parent6668012b673b6e2cffb46e27a267f2b02ef57eca (diff)
downloadpoky-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')
-rw-r--r--documentation/kernel-dev/kernel-dev-advanced.xml20
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 ba288d1..c9612c9 100644
--- a/documentation/kernel-dev/kernel-dev-advanced.xml
+++ b/documentation/kernel-dev/kernel-dev-advanced.xml
@@ -18,26 +18,6 @@
18 to help you manage the complexity of the configuration and sources 18 to help you manage the complexity of the configuration and sources
19 used to support multiple BSPs and Linux kernel types. 19 used to support multiple BSPs and Linux kernel types.
20 </para> 20 </para>
21
22 <para>
23 In particular, the kernel tools allow you to specify only what you
24 must, and nothing more.
25 Where a complete Linux kernel <filename>.config</filename> includes
26 all the automatically selected <filename>CONFIG</filename> options,
27 the configuration fragments only need to contain the highest level
28 visible <filename>CONFIG</filename> options as presented by the Linux
29 kernel <filename>menuconfig</filename> system.
30 This reduces your maintenance effort and allows you
31 to further separate your configuration in ways that make sense for
32 your project.
33 A common split is policy and hardware.
34 For example, all your kernels might support
35 the <filename>proc</filename> and <filename>sys</filename> filesystems,
36 but only specific boards will require sound, USB, or specific drivers.
37 Specifying these individually allows you to aggregate them
38 together as needed, but maintain them in only one place.
39 Similar logic applies to source changes.
40 </para>
41</section> 21</section>
42 22
43<section id='using-kernel-metadata-in-a-recipe'> 23<section id='using-kernel-metadata-in-a-recipe'>