From 9bf1cde472bb638a68dbf1a9c37252cbb736df90 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 16 Apr 2013 14:18:41 -0700 Subject: 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 Signed-off-by: Richard Purdie --- documentation/kernel-dev/kernel-dev-advanced.xml | 20 -------------------- 1 file changed, 20 deletions(-) (limited to 'documentation/kernel-dev') 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. - - - In particular, the kernel tools allow you to specify only what you - must, and nothing more. - Where a complete Linux kernel .config includes - all the automatically selected CONFIG options, - the configuration fragments only need to contain the highest level - visible CONFIG options as presented by the Linux - kernel menuconfig 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 proc and sys 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. -
-- cgit v1.2.3-54-g00ecf