sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

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:
Scott Rifenbark 2013-04-16 14:53:33 -07:00 committed by Richard Purdie
parent 6f2e173048
commit 77e10791c3
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
documentation/kernel-dev/kernel-dev-advanced.xml
View File

@ -30,7 +30,7 @@
This Metadata defines Board Support Packages (BSPs) that
correspond to definitions in linux-yocto recipes for the same BSPs.
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.
<note>
Linux kernel source that contains kernel Metadata is said to be
@ -787,7 +787,7 @@
</literallayout>
The <filename>include</filename> command midway through the file
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.
Using this command significantly reduces duplication.
</para>

6
documentation/kernel-dev/kernel-dev-common.xml
View File

@ -371,7 +371,7 @@
WARNING: There were 2 hardware options requested that do not
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:
meta/cfg/standard/mybsp/mismatch.cfg
</literallayout>
@ -725,7 +725,7 @@
"What changes have been applied to this tree?"
Rather than using "grep" across directories to see what has
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>
<section id='what-changed-in-a-kernel'>
@ -766,7 +766,7 @@
</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:
<literallayout class='monospaced'>
$ git log --oneline origin/standard/base..origin/standard/emenlow