[bootlin/training-materials updates] master: Kernel labs: use Linux 5.9 (ea185fd8)

Michael Opdenacker michael.opdenacker at bootlin.com
Fri Oct 23 16:59:32 CEST 2020

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


commit ea185fd8874653d1469ec0a1c717a11b0cd51d39
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Fri Oct 23 11:54:32 2020 +0200

    Kernel labs: use Linux 5.9
    - Instead of 5.5
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


 labs/kernel-i2c-device-model/kernel-i2c-device-model.tex   | 2 +-
 labs/kernel-module-simple/kernel-module-simple.tex         | 6 +++---
 labs/kernel-serial-iomem/kernel-serial-iomem.tex           | 2 +-
 labs/kernel-sources-download/kernel-sources-download.tex   | 2 +-
 labs/kernel-sources-exploring/kernel-sources-exploring.tex | 8 ++++----
 5 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex b/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex
index 8f29ee49..8f28b66c 100644
--- a/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex
+++ b/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex
@@ -17,7 +17,7 @@ device/driver match.
 Go to the \code{~/linux-kernel-labs/src/linux} directory. Check out the
-\code{5.5.y} branch.
+\code{5.9.y} branch.
 Now create a new \code{nunchuk} branch starting from the
 \code{5.5.y} branch,  for your upcoming work on the nunchuk
diff --git a/labs/kernel-module-simple/kernel-module-simple.tex b/labs/kernel-module-simple/kernel-module-simple.tex
index 661e39e2..6ca37d56 100644
--- a/labs/kernel-module-simple/kernel-module-simple.tex
+++ b/labs/kernel-module-simple/kernel-module-simple.tex
@@ -83,7 +83,7 @@ number of contributors, reading kernel code would be very unpleasant.
 Fortunately, the Linux kernel community provides you with a utility to
 find coding standards violations.
-First install the \code{python-ply} and \code{python-git} packages.
+First install the \code{python3-ply} and \code{python3-git} packages.
 Then run the \code{scripts/checkpatch.pl -h} command in the kernel sources,
 to find which options are available.  Now, run:
@@ -104,7 +104,7 @@ As we are going to make changes to the kernel sources, first create a
 special branch for such changes:
-git checkout 5.5.y
+git checkout 5.9.y
 git checkout -b hello
@@ -149,7 +149,7 @@ from the commits between your branch and another branch, usually the
 one you started from:
-git format-patch 5.5.y
+git format-patch 5.9.y
 Have a look at the generated file. You can see that its name reused
diff --git a/labs/kernel-serial-iomem/kernel-serial-iomem.tex b/labs/kernel-serial-iomem/kernel-serial-iomem.tex
index 82bf2fe4..dde7baaf 100644
--- a/labs/kernel-serial-iomem/kernel-serial-iomem.tex
+++ b/labs/kernel-serial-iomem/kernel-serial-iomem.tex
@@ -22,7 +22,7 @@ is independent from the nunchuk changes, it's best to create a separate
-git checkout 5.5.y
+git checkout 5.9.y
 git checkout -b uart
diff --git a/labs/kernel-sources-download/kernel-sources-download.tex b/labs/kernel-sources-download/kernel-sources-download.tex
index 94de303d..2a42a164 100644
--- a/labs/kernel-sources-download/kernel-sources-download.tex
+++ b/labs/kernel-sources-download/kernel-sources-download.tex
@@ -96,7 +96,7 @@ git fetch stable
-As this still represents many git objects to download (339 MiB when 5.5 was
+As this still represents many git objects to download (450 MiB when 5.9 was
 the latest version), if you are using an already downloaded git tree,
 your instructor will probably have fetched the {\em stable} branch ahead
 of time for you too. You can check by running:
diff --git a/labs/kernel-sources-exploring/kernel-sources-exploring.tex b/labs/kernel-sources-exploring/kernel-sources-exploring.tex
index ca3ab7b3..8492b7c5 100644
--- a/labs/kernel-sources-exploring/kernel-sources-exploring.tex
+++ b/labs/kernel-sources-exploring/kernel-sources-exploring.tex
@@ -26,18 +26,18 @@ cd ~/linux-kernel-labs/src/linux
 git branch -a
-As we will do our labs with the Linux 5.5 stable branch, the remote branch
-we are interested in is \code{remotes/stable/linux-5.5.y}.
+As we will do our labs with the Linux 5.9 stable branch, the remote branch
+we are interested in is \code{remotes/stable/linux-5.9.y}.
 First, open the \code{Makefile} file just to check the Linux kernel
 version that you currently have.
 Now, let's create a local branch starting from that remote branch:
-git checkout -b 5.5.y stable/linux-5.5.y
+git checkout -b 5.9.y stable/linux-5.9.y
-Open \code{Makefile} again and make sure you now have a 5.5.y version.
+Open \code{Makefile} again and make sure you now have a 5.9.y version.
 \section{Exploring the sources manually}

More information about the training-materials-updates mailing list