[FE training-materials-updates] Kernel frameworks: fix typos

Michael Opdenacker michael.opdenacker at free-electrons.com
Wed Oct 8 06:34:44 CEST 2014

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

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


commit e18695a7aa74caf04056c6507bffd4401d09779e
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Wed Oct 8 06:34:06 2014 +0200

    Kernel frameworks: fix typos
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


 slides/kernel-frameworks/kernel-frameworks.tex | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/slides/kernel-frameworks/kernel-frameworks.tex b/slides/kernel-frameworks/kernel-frameworks.tex
index 02fb4e8..bde04c4 100644
--- a/slides/kernel-frameworks/kernel-frameworks.tex
+++ b/slides/kernel-frameworks/kernel-frameworks.tex
@@ -595,8 +595,8 @@ struct rtl8150 {
   \frametitle{Link Between Structures 1/4}
   \item The framework typically contains a \kstruct{device} \code{*}
-    pointer that the driver must point to the corresponding struct
-    device
+    pointer that the driver must point to the corresponding
+    \kstruct{device}
     \item It's the relation between the logical device (for example a
       network interface) and the physical device (for example the USB
@@ -605,7 +605,7 @@ struct rtl8150 {
   \item The device structure also contains a \code{void *} pointer
     that the driver can freely use.
-    \item It's often use to link back the device to the higher-level
+    \item It's often used to link back the device to the higher-level
       structure from the framework.
     \item It allows, for example, from the \kstruct{platform_device}
       structure, to find the structure describing the logical device

More information about the training-materials-updates mailing list