[bootlin/training-materials updates] master: Linux kernel slides: minor fixes (9e2afe0f)

[Michael Opdenacker]

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

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

commit 9e2afe0f36db41f7cb5349e03a02e769b52739ba
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Fri Dec 18 13:45:58 2020 +0100

    Linux kernel slides: minor fixes
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

9e2afe0f36db41f7cb5349e03a02e769b52739ba
 .../kernel-driver-development-concurrency.tex                       | 6 ++----
 .../kernel-driver-development-interrupts.tex                        | 2 +-
 .../kernel-driver-development-io-memory.tex                         | 2 +-
 3 files changed, 4 insertions(+), 6 deletions(-)

diff --git a/slides/kernel-driver-development-concurrency/kernel-driver-development-concurrency.tex b/slides/kernel-driver-development-concurrency/kernel-driver-development-concurrency.tex
index c7d7166b..22d18c0b 100644
--- a/slides/kernel-driver-development-concurrency/kernel-driver-development-concurrency.tex
+++ b/slides/kernel-driver-development-concurrency/kernel-driver-development-concurrency.tex
@@ -141,10 +141,8 @@
     \item Doesn't disable interrupts. Used for locking in process
       context (critical sections in which you do not want to sleep).
     \end{itemize}
-  \item \mint{c}+void spin_lock_irqsave(spinlock_t *lock,+
-    \mint{c}+unsigned long flags);+
-  \item \mint{c}+void spin_unlock_irqrestore(spinlock_t *lock,+
-    \mint{c}+unsigned long flags);+
+  \item \mint{c}+void spin_lock_irqsave(spinlock_t *lock, unsigned long flags);+
+  \item \mint{c}+void spin_unlock_irqrestore(spinlock_t *lock, unsigned long flags);+
     \begin{itemize}
     \item Disables / restores IRQs on the local CPU.
     \item Typically used when the lock can be accessed in both process
diff --git a/slides/kernel-driver-development-interrupts/kernel-driver-development-interrupts.tex b/slides/kernel-driver-development-interrupts/kernel-driver-development-interrupts.tex
index f923059d..b3f0b963 100644
--- a/slides/kernel-driver-development-interrupts/kernel-driver-development-interrupts.tex
+++ b/slides/kernel-driver-development-interrupts/kernel-driver-development-interrupts.tex
@@ -251,7 +251,7 @@ int devm_request_threaded_irq(
     \item \kfunc{tasklet_schedule} to get it executed in
       \ksym{TASKLET_SOFTIRQ}
     \item \kfunc{tasklet_hi_schedule} to get it executed in
-      \ksym{HI_SOFTIRQ} (higher priority)
+      \ksym{HI_SOFTIRQ} (highest priority)
     \end{itemize}
   \end{itemize}
 \end{frame}
diff --git a/slides/kernel-driver-development-io-memory/kernel-driver-development-io-memory.tex b/slides/kernel-driver-development-io-memory/kernel-driver-development-io-memory.tex
index a93c2cdb..65a5d22d 100644
--- a/slides/kernel-driver-development-io-memory/kernel-driver-development-io-memory.tex
+++ b/slides/kernel-driver-development-io-memory/kernel-driver-development-io-memory.tex
@@ -238,7 +238,7 @@ __raw_writel(1 << KS8695_IRQ_UART_TX,
   \item Use the \kfunc{writel}/\kfunc{readl} macros,
         they do the right thing for your architecture
   \item The compiler and/or CPU can reorder memory accesses, which
-    might cause troubles for your devices is they expect one register
+    might cause trouble for your devices is they expect one register
     to be read/written before another one.
     \begin{itemize}
     \item Memory barriers are available to prevent this reordering