[bootlin/training-materials updates] master: kernel: sources: Rework the slide about in-tree drivers (4487d194)

[Miquel Raynal]

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

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

commit 4487d19404bc2f9417d1e35e404e2c677a28265a
Author: Miquel Raynal <miquel.raynal at bootlin.com>
Date:   Wed Nov 10 10:38:40 2021 +0100

    kernel: sources: Rework the slide about in-tree drivers
    
    This slide is more advertising the benefits of mainlining code more than
    organizing code. "in-tree" drivers do not mean that they are upstream
    (that was the purpose of one of the previous slides). Here we are
    talking about mainline code so rename the slide. Also rework a little
    bit the list of advantages, getting contributions from customers is
    anecdotal, getting reviews is actually useful and should be seen
    positively, a mainline driver will not suffer from API changes and will
    be compatible with all the kernel versions onward.
    
    Signed-off-by: Miquel Raynal <miquel.raynal at bootlin.com>


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

4487d19404bc2f9417d1e35e404e2c677a28265a
 .../kernel-source-code-drivers.tex                      | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

diff --git a/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex b/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex
index dab2dc0e..d43794bc 100644
--- a/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex
+++ b/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex
@@ -175,15 +175,16 @@
 \end{frame}
 
 \begin{frame}
-  \frametitle{Advantages of in-tree kernel drivers}
-  Once your sources are accepted in the mainline tree...
+  \frametitle{Advantages of mainlining your kernel drivers}
   \begin{itemize}
-  \item There are many more people reviewing your code, allowing to
-    get cost-free security fixes and improvements.
-  \item You can also get changes from people modifying internal
-    kernel APIs.
-  \item Accessing your code is easier for users.
-  \item You can get contributions from your own customers.
+  \item The community, reviewers and maintainers will review your code
+    before accepting it, offering you the opportunity to enhance it and
+    understand better the internal APIs.
+  \item Once accepted, you will get cost-free bug and security fixes,
+    support for new features, and general improvements.
+  \item Your work will automatically follow the API changes.
+  \item Accessing your code will be much easier for users.
+  \item Your code will remain valid no matter the kernel version.
   \end{itemize}
   This will for sure reduce your maintenance and support work
 \end{frame}