[BL training-materials-updates] Sysdev labs: upgrade to Linux 4.18

Michael Opdenacker michael.opdenacker at bootlin.com
Wed Oct 3 18:06:37 CEST 2018


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

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

commit dd60c19192e1e5ab4604d11985ae71a6511f0cec
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Wed Oct 3 18:06:37 2018 +0200

    Sysdev labs: upgrade to Linux 4.18
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

dd60c19192e1e5ab4604d11985ae71a6511f0cec
 .../sysdev-kernel-fetch-and-patch.tex                      | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex b/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex
index a0c1cb3..f0edc4b 100644
--- a/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex
+++ b/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex
@@ -19,18 +19,18 @@ identify the latest stable version.
 Just to make sure you know how to do it, check the version of the
 Linux kernel running on your machine.
 
-We will use \code{linux-4.14.x}, which this lab was tested with.
+We will use \code{linux-4.18.x}, which this lab was tested with.
 
-To practice with the \code{patch} command later, download the full 4.13
-sources. Unpack the archive, which creates a \code{linux-4.13}
+To practice with the \code{patch} command later, download the full 4.17
+sources. Unpack the archive, which creates a \code{linux-4.17}
 directory. Remember that you can use \code{wget <URL>} on the command
 line to download files.
 
 \section{Apply patches}
 
-Download the patch files corresponding to the latest 4.14 stable
-release: a first patch to move from 4.13 to 4.14 and if one exists,
-a second patch to move from 4.14 to 4.14.x.
+Download the patch files corresponding to the latest 4.18 stable
+release: a first patch to move from 4.17 to 4.18 and if one exists,
+a second patch to move from 4.18 to 4.18.x.
 
 Without uncompressing them (!), apply the patches to the Linux
 source directory.
@@ -39,4 +39,4 @@ View one of the 2 patch files with \code{vi} or \code{gvim}
 (if you prefer a graphical editor), to understand the information carried
 by such a file. How are described added or removed files?
 
-Rename the \code{linux-4.13} directory to \code{linux-4.14.<x>}.
+Rename the \code{linux-4.17} directory to \code{linux-4.18.<x>}.




More information about the training-materials-updates mailing list