kernel-dev: Spell checked the files and fixed appropriately.
(From yocto-docs rev: 0b9510d009f6437179c3848fc14c94af07ab99e2) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
6f2e173048
commit
77e10791c3
|
@ -30,7 +30,7 @@
|
||||||
This Metadata defines Board Support Packages (BSPs) that
|
This Metadata defines Board Support Packages (BSPs) that
|
||||||
correspond to definitions in linux-yocto recipes for the same BSPs.
|
correspond to definitions in linux-yocto recipes for the same BSPs.
|
||||||
A BSP consists of an aggregation of kernel policy and hardware-specific
|
A BSP consists of an aggregation of kernel policy and hardware-specific
|
||||||
feature enablement.
|
feature enablements.
|
||||||
The BSP can be influenced from within the linux-yocto recipe.
|
The BSP can be influenced from within the linux-yocto recipe.
|
||||||
<note>
|
<note>
|
||||||
Linux kernel source that contains kernel Metadata is said to be
|
Linux kernel source that contains kernel Metadata is said to be
|
||||||
|
@ -787,7 +787,7 @@
|
||||||
</literallayout>
|
</literallayout>
|
||||||
The <filename>include</filename> command midway through the file
|
The <filename>include</filename> command midway through the file
|
||||||
includes the <filename>fri2.scc</filename> description that
|
includes the <filename>fri2.scc</filename> description that
|
||||||
defines all hardware enablement for the BSP that is common to all
|
defines all hardware enablements for the BSP that is common to all
|
||||||
kernel types.
|
kernel types.
|
||||||
Using this command significantly reduces duplication.
|
Using this command significantly reduces duplication.
|
||||||
</para>
|
</para>
|
||||||
|
|
|
@ -371,7 +371,7 @@
|
||||||
|
|
||||||
WARNING: There were 2 hardware options requested that do not
|
WARNING: There were 2 hardware options requested that do not
|
||||||
have a corresponding value present in the final ".config" file.
|
have a corresponding value present in the final ".config" file.
|
||||||
This probably means you aren't getting the config you wanted.
|
This probably means you are not't getting the config you wanted.
|
||||||
The full list can be found in your kernel src dir at:
|
The full list can be found in your kernel src dir at:
|
||||||
meta/cfg/standard/mybsp/mismatch.cfg
|
meta/cfg/standard/mybsp/mismatch.cfg
|
||||||
</literallayout>
|
</literallayout>
|
||||||
|
@ -725,7 +725,7 @@
|
||||||
"What changes have been applied to this tree?"
|
"What changes have been applied to this tree?"
|
||||||
Rather than using "grep" across directories to see what has
|
Rather than using "grep" across directories to see what has
|
||||||
changed, you can use Git to inspect or search the kernel tree.
|
changed, you can use Git to inspect or search the kernel tree.
|
||||||
Using Git is an efficent way to see what has changed in the tree.
|
Using Git is an efficient way to see what has changed in the tree.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<section id='what-changed-in-a-kernel'>
|
<section id='what-changed-in-a-kernel'>
|
||||||
|
@ -766,7 +766,7 @@
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
To see short, oneline summaries of changes use the
|
To see short, one line summaries of changes use the
|
||||||
<filename>git log</filename> command:
|
<filename>git log</filename> command:
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
$ git log --oneline origin/standard/base..origin/standard/emenlow
|
$ git log --oneline origin/standard/base..origin/standard/emenlow
|
||||||
|
|
Loading…
Reference in New Issue