[bootlin/training-materials updates] master: sysdev-kernel-fetch-and-patch: update to 4.19 (8ee69d82)

[Alexandre Belloni]

Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/8ee69d82a4fefe5fefeb84d3671b31c32685aa98

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

commit 8ee69d82a4fefe5fefeb84d3671b31c32685aa98
Author: Alexandre Belloni <alexandre.belloni at bootlin.com>
Date:   Fri Apr 12 16:31:56 2019 +0200

    sysdev-kernel-fetch-and-patch: update to 4.19
    
    4.19 is needed to apply the stm32mp157 support patch.
    
    Signed-off-by: Alexandre Belloni <alexandre.belloni at bootlin.com>


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

8ee69d82a4fefe5fefeb84d3671b31c32685aa98
 .../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 4f16f8db..99433358 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.18.x}, which this lab was tested with.
+We will use \code{linux-4.19.x}, which this lab was tested with.
 
-To practice with the \code{patch} command later, download the full 4.17
-sources. Unpack the archive, which creates a \code{linux-4.17}
+To practice with the \code{patch} command later, download the full 4.18
+sources. Unpack the archive, which creates a \code{linux-4.18}
 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.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.
+Download the patch files corresponding to the latest 4.19 stable
+release: a first patch to move from 4.18 to 4.19 and if one exists,
+a second patch to move from 4.19 to 4.19.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.17} directory to \code{linux-4.18.<x>}.
+Rename the \code{linux-4.18} directory to \code{linux-4.19.<x>}.