replace *all* tabs with spaces

There are times when tabs are allowed and times when they are not.
Let's just simply never use tabs for anything. This makes it easy
to find presentations where tabs were accidentally inserted.

Signed-off-by: John Ogness <john.ogness@linutronix.de>

6 files changed, 23 insertions, 23 deletions

diff --git a/kernel-devel/kernel-basics/hints_kernel-basics_de.tex b/kernel-devel/kernel-basics/hints_kernel-basics_de.tex
index c81b6f5..23fd5cc 100644
--- a/kernel-devel/kernel-basics/hints_kernel-basics_de.tex
+++ b/kernel-devel/kernel-basics/hints_kernel-basics_de.tex
@@ -12,7 +12,7 @@
 \item Verstehen des Entwicklungsprozesses (Patche, Review)
 \item Kennenlernen des Buildsystems (make menuconfig)
 \item Kennenlerne grundsätzlicher Kernel-Ziele (Skalierbarkeit,
-	Plattformunabhängigkeit)
+        Plattformunabhängigkeit)
 \end{itemize}
 
 \subsection*{Unterrichts-Ablauf}
diff --git a/kernel-devel/kernel-basics/pres_kernel-basics_de.tex b/kernel-devel/kernel-basics/pres_kernel-basics_de.tex
index 9e53fd5..08f34f4 100644
--- a/kernel-devel/kernel-basics/pres_kernel-basics_de.tex
+++ b/kernel-devel/kernel-basics/pres_kernel-basics_de.tex
@@ -225,9 +225,9 @@ Versionssprünge
 \end{frame}
 
 \begin{frame}
-	\includegraphics[height=6cm]{images/kernelversions.png}
+\includegraphics[height=6cm]{images/kernelversions.png}
 
-	Quelle: http://article.sapub.org
+Quelle: http://article.sapub.org
 \end{frame}
 
 
diff --git a/kernel-devel/kernel-best-practices/handout_kernel-best-practices_en.tex b/kernel-devel/kernel-best-practices/handout_kernel-best-practices_en.tex
index bd1140b..ac39c19 100644
--- a/kernel-devel/kernel-best-practices/handout_kernel-best-practices_en.tex
+++ b/kernel-devel/kernel-best-practices/handout_kernel-best-practices_en.tex
@@ -18,7 +18,7 @@ orig/hello.c
 \begin{lstlisting}
 int main (int argc, char **argv)
 {
-	return 0;
+    return 0;
 }
 \end{lstlisting}
 
@@ -37,8 +37,8 @@ new/hello.c
 
 int main (int argc, char **argv)
 {
-	printf ("Huhu World\n");
-	return 0;
+    printf ("Huhu World\n");
+    return 0;
 }
 \end{lstlisting}
 
@@ -110,7 +110,7 @@ orig/hello.c
 \begin{lstlisting}
 int main (int argc, char **argv)
 {
-	return 0;
+    return 0;
 }
 \end{lstlisting}
 
@@ -129,8 +129,8 @@ your default editor will be opened, make your changes to the source:
 
 int main (int argc, char **argv)
 {
-	printf ("Huhu World\n");
-	return 0;
+    printf ("Huhu World\n");
+    return 0;
 }
 \end{lstlisting}
 
@@ -219,7 +219,7 @@ orig/hello.c
 \begin{lstlisting}
 int main (int argc, char **argv)
 {
-	return 0;
+    return 0;
 }
 \end{lstlisting}
 
diff --git a/kernel-devel/kernel-best-practices/hints_kernel-best-practices_de.tex b/kernel-devel/kernel-best-practices/hints_kernel-best-practices_de.tex
index ce4c69a..57f9c09 100644
--- a/kernel-devel/kernel-best-practices/hints_kernel-best-practices_de.tex
+++ b/kernel-devel/kernel-best-practices/hints_kernel-best-practices_de.tex
@@ -12,7 +12,7 @@
 \item Verstehen, warum strikte Coding-Style-Regeln wichtig sind
 \item Verstehen, warum man einen aktuellen Kernel verwenden sollte
 \item Kennenlernen der Möglichkeiten und Vorteile der Zusammenarbeit
-	mit der Community (Mailinglisten, IRC, Wikis...)
+        mit der Community (Mailinglisten, IRC, Wikis...)
 \end{itemize}
 
 \subsection*{Unterrichts-Ablauf}
diff --git a/kernel-devel/kernel-build/handout_kernel-build_de.tex b/kernel-devel/kernel-build/handout_kernel-build_de.tex
index bd28a31..0e96858 100644
--- a/kernel-devel/kernel-build/handout_kernel-build_de.tex
+++ b/kernel-devel/kernel-build/handout_kernel-build_de.tex
@@ -174,11 +174,11 @@ make install
 Dies führt folgende Aktionen durch (Beispiel für einen Kernel 2.6.30):
 \begin{itemize}
 \item Falls es im Verzeichnis \cmd{/boot} bereits ein \cmd{vmlinuz-2.6.30}
-	gibt, wird es in \cmd{vmlinuz-2.6.30.old} umbenannt
+        gibt, wird es in \cmd{vmlinuz-2.6.30.old} umbenannt
 \item Kopieren von \cmd{arch/<Architektur-Name>/boot/zImage} nach
-	\cmd{/boot/vmlinuz-2.6.30}
+        \cmd{/boot/vmlinuz-2.6.30}
 \item Anlegen eines symbolischen Link \cmd{vmlinuz -> vmlinuz-2.6.30} in
-	\cmd{/boot}
+        \cmd{/boot}
 \end{itemize}
 
 Anschliessend darf man nicht vergessen, auch die Module des neuen Kernels
@@ -216,7 +216,7 @@ Entwicklung von Treibern für Embedded Systems sehr bewährt.
 \begin{enumerate}
 \item Beschreiben Sie Unterschiede zwischen initrd und initramfs.
 \item Warum braucht man bei selbst kompilierten Kerneln in der Regel keine
-	initrd?
+        initrd?
 \item Nennen Sie eine Anwendung von initramfs.
 \end{enumerate}
 
diff --git a/kernel-devel/kernel-debugging/pres_kernel-debugging_en.tex b/kernel-devel/kernel-debugging/pres_kernel-debugging_en.tex
index 62624a9..5e9d30f 100644
--- a/kernel-devel/kernel-debugging/pres_kernel-debugging_en.tex
+++ b/kernel-devel/kernel-debugging/pres_kernel-debugging_en.tex
@@ -152,7 +152,7 @@ console=ttyAM0,115200
 Kernel commandline:
 \begin{verbatim}
 netconsole=[src-port]@[src-ip]/[<dev>],
-		[tgt-port]@<tgt-ip>/[tgt-macaddr]
+                [tgt-port]@<tgt-ip>/[tgt-macaddr]
 \end{verbatim}
 src-port defaults to 6665. tgt-port defaults to 6666.
 \begin{verbatim}
@@ -301,7 +301,7 @@ Continuing.
 
 Breakpoint 1, start_kernel ()
     at linux-2.6.37-rc4/init/main.c:539
-539		smp_setup_processor_id();
+539             smp_setup_processor_id();
 \end{verbatim}
 \end{frame}
 
@@ -363,7 +363,7 @@ Remote debugging using localhost:2345
 
 kgdb_breakpoint ()
     at linux-2.6.37-rc4/kernel/debug/debug_core.c:959
-959		arch_kgdb_breakpoint();
+959             arch_kgdb_breakpoint();
 (gdb) 
 \end{verbatim}
 \end{frame}
@@ -413,8 +413,8 @@ mount your hosts / to /mnt/myhost
 \begin{lstlisting}[language=bash]
 $ gdb ./linux
 (gdb) handle SIGSEGV pass nostop noprint
-Signal        Stop	Print	Pass to program	Description
-SIGSEGV       No	No	Yes		Segmentation fault
+Signal        Stop      Print   Pass to program Description
+SIGSEGV       No        No      Yes             Segmentation fault
 (gdb) b start_kernel
 Breakpoint 1 at 0x80493ca: file /home/devel/images/linux-2.6.37/init/main.c,
 line 539.
@@ -423,14 +423,14 @@ Starting program: /home/devel/images/build_um/linux
 Locating the bottom of the address space ... 0x1000
 Locating the top of the address space ... 0xc0000000
 Core dump limits :
-	soft - 0
-	hard - NONE
+        soft - 0
+        hard - NONE
 [...]
 Adding 10047488 bytes to physical memory to account for exec-shield gap
 
 Breakpoint 1, start_kernel () at
 /home/devel/images/linux-2.6.37/init/main.c:539
-539		smp_setup_processor_id();
+539             smp_setup_processor_id();
 (gdb) c 
 Continuing.
 Linux version 2.6.37 (devel@ltx) (gcc version 4.3.2 (Debian 4.3.2-1.1) )