kernel-dev: Applied review comments to "Adding Recipe-Space Kernel Features"
Fixes [YOCTO #4047] I went through and fixed a few areas where reviewers said there was "quirky" phrasing. They might have been right in a few places. (From yocto-docs rev: 66fb97838f338ed3f787ec18f62702ef726ceffc) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
d57fe7c98c
commit
ee42a9b73e
|
@ -1041,8 +1041,8 @@
|
||||||
<link linkend='recipe-space-metadata'>recipe-space</link> by
|
<link linkend='recipe-space-metadata'>recipe-space</link> by
|
||||||
using the
|
using the
|
||||||
<ulink url='&YOCTO_DOCS_REF_URL;#var-KERNEL_FEATURES'><filename>KERNEL_FEATURES</filename></ulink>
|
<ulink url='&YOCTO_DOCS_REF_URL;#var-KERNEL_FEATURES'><filename>KERNEL_FEATURES</filename></ulink>
|
||||||
variable along with specifying the <filename>.scc</filename> file
|
variable and by specifying the feature's <filename>.scc</filename>
|
||||||
path on the
|
file path in the
|
||||||
<ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink>
|
<ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink>
|
||||||
statement.
|
statement.
|
||||||
When you add features using this method, the OpenEmbedded build
|
When you add features using this method, the OpenEmbedded build
|
||||||
|
@ -1051,7 +1051,7 @@
|
||||||
Kernel features are the last elements processed for configuring
|
Kernel features are the last elements processed for configuring
|
||||||
and patching the kernel.
|
and patching the kernel.
|
||||||
Therefore, adding features in this manner is a way
|
Therefore, adding features in this manner is a way
|
||||||
to enforce that specific features are present, and enabled,
|
to enforce specific features are present and enabled
|
||||||
without needing to do a full audit of any other layer's additions
|
without needing to do a full audit of any other layer's additions
|
||||||
to the <filename>SRC_URI</filename> statement.
|
to the <filename>SRC_URI</filename> statement.
|
||||||
</para>
|
</para>
|
||||||
|
@ -1074,7 +1074,7 @@
|
||||||
When you specify the feature's <filename>.scc</filename> file
|
When you specify the feature's <filename>.scc</filename> file
|
||||||
on the <filename>SRC_URI</filename> statement, the OpenEmbedded
|
on the <filename>SRC_URI</filename> statement, the OpenEmbedded
|
||||||
build system adds the directory of that
|
build system adds the directory of that
|
||||||
<filename>.scc</filename> file, and all its subdirectories,
|
<filename>.scc</filename> file along with all its subdirectories
|
||||||
to the kernel feature search path.
|
to the kernel feature search path.
|
||||||
Because subdirectories are searched, you can reference a single
|
Because subdirectories are searched, you can reference a single
|
||||||
<filename>.scc</filename> file in the
|
<filename>.scc</filename> file in the
|
||||||
|
@ -1095,11 +1095,10 @@
|
||||||
<note><title>Notes</title>
|
<note><title>Notes</title>
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem><para>
|
<listitem><para>
|
||||||
The directory you use for the
|
You must add the directory of the
|
||||||
<filename>.scc</filename> must be added to the
|
<filename>.scc</filename> file to the fetcher's
|
||||||
fetcher search directory just as you would,
|
search path in the same manner as you would
|
||||||
for example, if you were adding a
|
add a <filename>.patch</filename> file.
|
||||||
<filename>.patch</filename> file.
|
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
<listitem><para>
|
<listitem><para>
|
||||||
You can create additional
|
You can create additional
|
||||||
|
|
Loading…
Reference in New Issue