[FE training-materials-updates] kernel-driver-development-processes: after fork(), we don't run main()

[Thomas Petazzoni]

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

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

commit 9d58d9855ba33d2392bd0878585e4914b797907a
Author: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
Date:   Thu Nov 17 09:37:29 2016 +0100

    kernel-driver-development-processes: after fork(), we don't run main()
    
    After a fork(), the single thread of a process doesn't run the main()
    function, it continues the execution from the point where fork()
    returned.
    
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>


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

9d58d9855ba33d2392bd0878585e4914b797907a
 .../kernel-driver-development-processes.tex                             | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/slides/kernel-driver-development-processes/kernel-driver-development-processes.tex b/slides/kernel-driver-development-processes/kernel-driver-development-processes.tex
index a0dc58d..ed45b1b 100644
--- a/slides/kernel-driver-development-processes/kernel-driver-development-processes.tex
+++ b/slides/kernel-driver-development-processes/kernel-driver-development-processes.tex
@@ -12,7 +12,7 @@
     \begin{itemize}
     \item An address space, which contains the program code, data,
       stack, shared libraries, etc.
-    \item One thread, that starts executing the \code{main()}
+    \item One thread, entity known by the scheduler.
       function.
     \item Upon creation, a process contains one thread
     \end{itemize}