[FE training-materials-updates] kernel debugging: remove trivial statement

[Michael Opdenacker]

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

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

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

commit 2187299ca8c4d0c4d5008ff72fa0b788bf3e42ba
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Fri Oct 4 18:20:34 2013 +0200

    kernel debugging: remove trivial statement
    
    (at least trivial at that stage in the labs)
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


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

2187299ca8c4d0c4d5008ff72fa0b788bf3e42ba
 labs/kernel-debugging/kernel-debugging.tex |    3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/labs/kernel-debugging/kernel-debugging.tex b/labs/kernel-debugging/kernel-debugging.tex
index 7ff8e7c..c405c01 100644
--- a/labs/kernel-debugging/kernel-debugging.tex
+++ b/labs/kernel-debugging/kernel-debugging.tex
@@ -94,8 +94,7 @@ register contains the location of the instruction being executed, find
 in which function does the crash happens, and what the function call
 stack is.
 
-Using LXR (for example \url{http://lxr.free-electrons.com}) or the
-kernel source code, have a look at the definition of this
+Using LXR or the kernel source code, have a look at the definition of this
 function. This, with a careful review of the driver source code should
 probably be enough to help you understand and fix the issue.