summaryrefslogtreecommitdiffstats
path: root/documentation/kernel-dev
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2015-03-03 10:00:39 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-03-06 10:44:37 +0000
commit82ad008cd20f26fec104f662d3dd7526973a2272 (patch)
tree2cbccb803ec2f29dcb4fdf9749a74437773c5106 /documentation/kernel-dev
parent86f4cf8fafeeab9f53ea0fbaacf6c0caeb4fbf13 (diff)
downloadpoky-82ad008cd20f26fec104f662d3dd7526973a2272.tar.gz
kernel-dev: Updated "Modifying Source Code" section.
Substituted a more correct build directory path in the example by providing "${WORKDIR}/linux-${PACKAGE_ARCH}-${LINUX_KERNEL_TYPE}-build" Reported-by: Robert P. J. Day <rpjday@crashcourse.ca> (From yocto-docs rev: 818493d7ee5fc6c1750f20e5cea22a3816c8675c) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.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 90a4f3876f..e16b9e79a4 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -477,9 +477,9 @@
477 the <filename>compile</filename>. 477 the <filename>compile</filename>.
478 Once compilation is successful, you can inspect and test 478 Once compilation is successful, you can inspect and test
479 the resulting build (i.e. kernel, modules, and so forth) from 479 the resulting build (i.e. kernel, modules, and so forth) from
480 the <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>: 480 the following build directory:
481 <literallayout class='monospaced'> 481 <literallayout class='monospaced'>
482 ${WORKDIR}/linux-${MACHINE}-${KTYPE}-build 482 ${WORKDIR}/linux-${PACKAGE_ARCH}-${LINUX_KERNEL_TYPE}-build
483 </literallayout> 483 </literallayout>
484 Alternatively, you can run the <filename>deploy</filename> 484 Alternatively, you can run the <filename>deploy</filename>
485 command to place the kernel image in the 485 command to place the kernel image in the