From: Scott Rifenbark <srifenbark@gmail.com>
Date: Thu, 15 Nov 2018 22:30:15 +0000 (-0800)
Subject: kernel-dev: Updated phrasing for what a "defconfig" file is.
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=58128d2b32420b788e587dfeede6cae3e5ab4476;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git

kernel-dev: Updated phrasing for what a "defconfig" file is.

It was over simplistic.

(From yocto-docs rev: 1c17e3ef607d18c89c3e20d2d44eb5120779cd2c)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---

diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml
index 83b02b1c18e..9052876122d 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -1603,8 +1603,11 @@
             <title>Creating a&nbsp;&nbsp;<filename>defconfig</filename> File</title>
 
             <para>
-                A <filename>defconfig</filename> file is simply a
-                <filename>.config</filename> renamed to "defconfig".
+                A <filename>defconfig</filename> file in the context of
+                the Yocto Project is often a <filename>.config</filename>
+                file that is copied from a build or a
+                <filename>defconfig</filename> taken from the kernel tree
+                and moved into recipe space.
                 You can use a <filename>defconfig</filename> file
                 to retain a known set of kernel configurations from which the
                 OpenEmbedded build system can draw to create the final