bsp-guide, kernel-dev: Added Cross-references to "BitBake" term

I made sure that the first occurrence of each "BitBake" term linked
into the "BitBake" term as defined in the dev-manual.

(From yocto-docs rev: 83e6e43d13cf5447b8ef65836d532abbb1f8b15e)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 10 insertions, 8 deletions

diff --git a/documentation/kernel-dev/kernel-dev-advanced.xml b/documentation/kernel-dev/kernel-dev-advanced.xml
index 4589e4b9fc..64d8110576 100644
--- a/documentation/kernel-dev/kernel-dev-advanced.xml
+++ b/documentation/kernel-dev/kernel-dev-advanced.xml
@@ -47,7 +47,9 @@
         variable.
         This variable is typically set to the same value as the
         <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
-        variable, which is used by BitBake (e.g. "routerstationpro" or "fri2").
+        variable, which is used by
+        <ulink url='&YOCTO_DOCS_DEV_URL;#bitbake-term'>BitBake</ulink>
+        (e.g. "routerstationpro" or "fri2").
         Multiple BSPs can reuse the same <filename>KMACHINE</filename>
         name if they are built using the same BSP description.
         The "fri2" and "fri2-noemgd" BSP combination
@@ -298,16 +300,16 @@
         </para>
 
         <para>
-            If you modify the Metadata in the linux-yocto 
-            <filename>meta</filename> branch, you must not forget to update 
-            the 
+            If you modify the Metadata in the linux-yocto
+            <filename>meta</filename> branch, you must not forget to update
+            the
             <ulink url='&YOCTO_DOCS_REF_URL;#var-SRCREV'><filename>SRCREV</filename></ulink>
             statements in the kernel's recipe.
-            In particular, you need to update the 
-            <filename>SRCREV_meta</filename> variable to match the commit in 
+            In particular, you need to update the
+            <filename>SRCREV_meta</filename> variable to match the commit in
             the <filename>KMETA</filename> branch you wish to use.
-            Changing the data in these branches and not updating the 
-            <filename>SRCREV</filename> statements to match will cause the 
+            Changing the data in these branches and not updating the
+            <filename>SRCREV</filename> statements to match will cause the
             build to fetch an older commit.
         </para>
     </section>