[bootlin/training-materials updates] master: Kernel labs: switch to Linux 5.11 (0adef38a)
Thomas Petazzoni
thomas.petazzoni at bootlin.com
Fri Oct 29 10:46:36 CEST 2021
Repository : https://github.com/bootlin/training-materials
On branch : master
Link : https://github.com/bootlin/training-materials/commit/0adef38af54db448fb6158ac2faae2f8e6983069
>---------------------------------------------------------------
commit 0adef38af54db448fb6158ac2faae2f8e6983069
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date: Fri Apr 23 16:09:26 2021 +0200
Kernel labs: switch to Linux 5.11
Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>
>---------------------------------------------------------------
0adef38af54db448fb6158ac2faae2f8e6983069
labs/kernel-i2c-device-model/kernel-i2c-device-model.tex | 4 ++--
labs/kernel-module-simple/kernel-module-simple.tex | 4 ++--
labs/kernel-serial-iomem/kernel-serial-iomem.tex | 2 +-
labs/kernel-sources-exploring/kernel-sources-exploring.tex | 8 ++++----
4 files changed, 9 insertions(+), 9 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 0c9ddd6e..9c98d993 100644
--- a/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex
+++ b/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex
@@ -17,10 +17,10 @@ device/driver match.
\section{Setup}
Go to the \code{~/linux-kernel-labs/src/linux} directory. Check out the
-\code{5.10.y} branch.
+\code{5.11.y} branch.
Now create a new \code{nunchuk} branch starting from the
-\code{5.10.y} branch, for your upcoming work on the nunchuk
+\code{5.11.y} branch, for your upcoming work on the nunchuk
driver.
During this lab, we will start to implement a driver for a
diff --git a/labs/kernel-module-simple/kernel-module-simple.tex b/labs/kernel-module-simple/kernel-module-simple.tex
index f8888d59..16c0efb9 100644
--- a/labs/kernel-module-simple/kernel-module-simple.tex
+++ b/labs/kernel-module-simple/kernel-module-simple.tex
@@ -104,7 +104,7 @@ As we are going to make changes to the kernel sources, first create a
special branch for such changes:
\begin{verbatim}
-git checkout 5.10.y
+git checkout 5.11.y
git checkout -b hello
\end{verbatim}
@@ -149,7 +149,7 @@ from the commits between your branch and another branch, usually the
one you started from:
\begin{verbatim}
-git format-patch 5.10.y
+git format-patch 5.11.y
\end{verbatim}
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 b89ff108..f2d76997 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
branch!
\begin{verbatim}
-git checkout 5.10.y
+git checkout 5.11.y
git checkout -b uart
\end{verbatim}
diff --git a/labs/kernel-sources-exploring/kernel-sources-exploring.tex b/labs/kernel-sources-exploring/kernel-sources-exploring.tex
index 617536e6..dbfcd003 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
\end{verbatim}
-As we will do our labs with the Linux 5.10 stable branch, the remote branch
-we are interested in is \code{remotes/stable/linux-5.10.y}.
+As we will do our labs with the Linux 5.11 stable branch, the remote branch
+we are interested in is \code{remotes/stable/linux-5.11.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:
\begin{verbatim}
-git checkout -b 5.10.y stable/linux-5.10.y
+git checkout -b 5.11.y stable/linux-5.11.y
\end{verbatim}
-Open \code{Makefile} again and make sure you now have a 5.10.y version.
+Open \code{Makefile} again and make sure you now have a 5.11.y version.
\section{Exploring the sources manually}
More information about the training-materials-updates
mailing list