summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual/common-tasks.rst
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/dev-manual/common-tasks.rst')
-rw-r--r--documentation/dev-manual/common-tasks.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/documentation/dev-manual/common-tasks.rst b/documentation/dev-manual/common-tasks.rst
index 7f51674a92..4a5011ea74 100644
--- a/documentation/dev-manual/common-tasks.rst
+++ b/documentation/dev-manual/common-tasks.rst
@@ -2064,7 +2064,7 @@ Now comes the time to actually build an image and you need a kernel
2064recipe, but which one? You can configure your build to call out the 2064recipe, but which one? You can configure your build to call out the
2065kernel recipe you want by using the :term:`PREFERRED_PROVIDER` variable. As 2065kernel recipe you want by using the :term:`PREFERRED_PROVIDER` variable. As
2066an example, consider the :yocto_git:`x86-base.inc 2066an example, consider the :yocto_git:`x86-base.inc
2067</poky/tree/meta/conf/machine/include/x86-base.inc>` include file, which is a 2067</poky/tree/meta/conf/machine/include/x86/x86-base.inc>` include file, which is a
2068machine (i.e. :term:`MACHINE`) configuration file. This include file is the 2068machine (i.e. :term:`MACHINE`) configuration file. This include file is the
2069reason all x86-based machines use the ``linux-yocto`` kernel. Here are the 2069reason all x86-based machines use the ``linux-yocto`` kernel. Here are the
2070relevant lines from the include file:: 2070relevant lines from the include file::