[FE training-materials-updates] Kernel slides: add details about /include/ vs #include

[Michael Opdenacker]

Repository : git://git.free-electrons.com/training-materials.git

On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=4dfd7122334ce78b270e0c11603c569a12c8a8ac

>---------------------------------------------------------------

commit 4dfd7122334ce78b270e0c11603c569a12c8a8ac
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Tue Feb 4 15:48:43 2014 +0100

    Kernel slides: add details about /include/ vs #include
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


>---------------------------------------------------------------

4dfd7122334ce78b270e0c11603c569a12c8a8ac
 slides/kernel-device-model/kernel-device-model.tex |   11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/slides/kernel-device-model/kernel-device-model.tex b/slides/kernel-device-model/kernel-device-model.tex
index e8fa3ed..3270abb 100644
--- a/slides/kernel-device-model/kernel-device-model.tex
+++ b/slides/kernel-device-model/kernel-device-model.tex
@@ -609,7 +609,16 @@ uart0: serial at 44e09000 {
     similarities.
   \item To allow this, a {\em device tree} file can include another
     one. The trees described by the including file overlays the tree
-    described by the included file.
+    described by the included file. This can be done:
+    \begin{itemize}
+       \item Either by using the \code{/include/} statement 
+	     provided by the Device Tree language. 
+       \item Either by using the \code{\#include} statement,
+   	     which requires calling the C preprocessor before
+             parsing the Device Tree.
+    \end{itemize}
+    Linux currently uses either one technique or the other,
+    (different from one ARM subarchitecture to another, for example).
   \end{itemize}
 \end{frame}