[FE training-materials-updates] kernel: interrupts: tell that we need to register the interrupt in probe, and not init

[Maxime Ripard]

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

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

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

commit 7f80c1f720e45023ae3d63e00a096bd04a351ffe
Author: Maxime Ripard <maxime.ripard at free-electrons.com>
Date:   Mon Oct 14 15:20:13 2013 +0200

    kernel: interrupts: tell that we need to register the interrupt in probe, and not init
    
    Signed-off-by: Maxime Ripard <maxime.ripard at free-electrons.com>


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

7f80c1f720e45023ae3d63e00a096bd04a351ffe
 .../kernel-serial-interrupt.tex                    |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex b/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex
index 42b4e29..91800ce 100644
--- a/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex
+++ b/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex
@@ -22,9 +22,9 @@ lab}. Use the same kernel, environment and paths!
 
 \section{Register the handler}
 
-Declare an interrupt handler function stub. Then, in the module
-initialization function, we need to register this handler, binding
-it to the right IRQ number.
+Declare an interrupt handler function stub. Then, in the module probe
+function, we need to register this handler, binding it to the right
+IRQ number.
 
 Nowadays, Linux is using a virtual IRQ number that it derives from the
 hardware interrupt number. This virtual number is created through the