kernel-dev: Removed recursive include statement from examples.

Three instances of *.scc files were recursively including themselves.
These .scc files needed to have their names changed to a file
that indicated hardware support only.

(From yocto-docs rev: f1c347f8f63141807084ac0a2bd3b64e138315cb)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2013-01-09 16:20:14 -08:00
committed by Richard Purdie
parent b56df9790e
commit f42c87a1ac

View File

@@ -1123,7 +1123,7 @@ Note: It is not strictly necessary to create a ktype scc file. The BSP file can
define KARCH i386 define KARCH i386
include standard.scc include standard.scc
include mybsp.scc include mybsp-hw.scc
</literallayout> </literallayout>
</para> </para>
@@ -1131,7 +1131,7 @@ Note: It is not strictly necessary to create a ktype scc file. The BSP file can
In the above example, <filename>standard.scc</filename> In the above example, <filename>standard.scc</filename>
aggregates all the configuration fragments, patches, and aggregates all the configuration fragments, patches, and
features that make up your standard kernel policy whereas features that make up your standard kernel policy whereas
<filename>mybsp.scc</filename> aggregates all those necessary <filename>mybsp-hw.scc</filename> aggregates all those necessary
to support the hardware available on the "mybsp" machine. to support the hardware available on the "mybsp" machine.
For information on how to break a complete For information on how to break a complete
<filename>.config</filename> file into the various <filename>.config</filename> file into the various
@@ -1373,9 +1373,6 @@ the KTYPE has changed, now set to "tiny".
</section> </section>
</section> </section>
<section id='machine-branches'> <section id='machine-branches'>
<title>Machine Branches</title> <title>Machine Branches</title>
@@ -1425,7 +1422,7 @@ the KTYPE has changed, now set to "tiny".
branch mynewbranch branch mynewbranch
include mybsp.scc include mybsp-hw.scc
</literallayout> </literallayout>
</para> </para>
@@ -1580,7 +1577,7 @@ Note: The "base" branches are an artifact of the way git manages its data
branch mynewbranch branch mynewbranch
git merge myfeature git merge myfeature
include mybsp.scc include mybsp-hw.scc
</literallayout> </literallayout>
</para> </para>