[FE training-materials-updates] Remove the slide "How To Create Kernel Patches"

[Thomas Petazzoni]

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

On branch  : kernel-ng
Link       : http://git.free-electrons.com/training-materials/commit/?id=ec091fe17485458ad01d15b8c7abe8ca28de4372

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

commit ec091fe17485458ad01d15b8c7abe8ca28de4372
Author: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
Date:   Thu Sep 12 11:42:01 2013 +0200

    Remove the slide "How To Create Kernel Patches"
    
    Since we're moving away from tarballs, doing patches with diff no
    longer makes sense. Talking about the Git details here is really
    moving away from the scope of the training, so just remove this.
    
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>


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

ec091fe17485458ad01d15b8c7abe8ca28de4372
 .../kernel-driver-development-modules.tex          |   22 --------------------
 1 file changed, 22 deletions(-)

diff --git a/slides/kernel-driver-development-modules/kernel-driver-development-modules.tex b/slides/kernel-driver-development-modules/kernel-driver-development-modules.tex
index 7afb46d..3f84bcd 100644
--- a/slides/kernel-driver-development-modules/kernel-driver-development-modules.tex
+++ b/slides/kernel-driver-development-modules/kernel-driver-development-modules.tex
@@ -266,28 +266,6 @@ config USB_SERIAL_NAVMAN
   \end{itemize}
 \end{frame}
 
-\begin{frame}
-  \frametitle{How To Create Linux Patches}
-  \begin{itemize}
-  \item The old school way
-    \begin{itemize}
-    \item Before making your changes, make sure you have two kernel
-      trees: \code{cp -a linux-3.5.5/ linux-3.5.5-patch/}
-    \item Make your changes in \code{linux-3.5.5-patch/}
-    \item Run \code{make distclean} to keep only source files.
-    \item Create a patch file:
-      \code{diff -Nur linux-3.5.5/ linux-3.5.5-patch/ > patchfile}
-    \item Not convenient, does not scale to multiple patches
-    \end{itemize}
-  \item The new school ways
-    \begin{itemize}
-    \item Use \code{quilt} (tool to manage a stack of patches)
-    \item Use \code{git} (revision control system used by the Linux kernel
-      developers)
-    \end{itemize}
-  \end{itemize}
-\end{frame}
-
 \begin{frame}[fragile]
   \frametitle{Hello Module with Parameters 1/2}
 \begin{minted}[fontsize=\small]{c}