summaryrefslogtreecommitdiffstats
path: root/documentation/kernel-dev
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2018-04-15 12:47:32 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2018-05-24 17:16:16 +0100
commitddc6ef5273174379f4ed2747777bd9aef330bb17 (patch)
tree673b632ba52c0a50f7fa223ad65fe403e77a201d /documentation/kernel-dev
parent65cb5fdf7925bee96c9e8de26884c0f203ff54a8 (diff)
downloadopenembedded-core-contrib-ddc6ef5273174379f4ed2747777bd9aef330bb17.tar.gz
kernel-dev: Minor fixes.
1. Fixed the name of the "do_compile" task so that it was not referenced as "do_compile()". 2. Fixed a link to the Source Repositories so that the link used the ENTITY for the YP Git area and not a full-blown hard-coded path. (From yocto-docs rev: 4b8d0e61f3f3017954d36ed196a08fb0a04909dc) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/kernel-dev')
-rw-r--r--documentation/kernel-dev/kernel-dev-common.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml
index c502813d6d..1a0c7e4c33 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -2418,7 +2418,7 @@
modules.
If your module <filename>Makefile</filename> uses a different
variable, you might want to override the
- <ulink url='&YOCTO_DOCS_REF_URL;#ref-tasks-compile'><filename>do_compile()</filename></ulink>
+ <ulink url='&YOCTO_DOCS_REF_URL;#ref-tasks-compile'><filename>do_compile</filename></ulink>
step, or create a patch to
the <filename>Makefile</filename> to work with the more typical
<filename>KERNEL_SRC</filename> or
@@ -2494,7 +2494,7 @@
the Git commands.
You can see the branch names through the web interface
to the Yocto Project source repositories at
- <ulink url='http://git.yoctoproject.org/cgit.cgi'></ulink>.
+ <ulink url='&YOCTO_GIT_URL;'></ulink>.
</note>
To see a full range of the changes, use the
<filename>git whatchanged</filename> command and specify a