[FE training-materials-updates] Trainer presentation slide for Mylène

[Michael Opdenacker]

Repository : git://git.free-electrons.com/training-materials.git
On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=5ec1cc29496c90fe3d10dbbcdf3539d75221cfd4

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

commit 5ec1cc29496c90fe3d10dbbcdf3539d75221cfd4
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Tue Jan 10 16:24:55 2017 +0100

    Trainer presentation slide for Mylène
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


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

5ec1cc29496c90fe3d10dbbcdf3539d75221cfd4
 slides/first-slides/mylene-josserand.tex           | 12 +++++
 slides/kernel-contribution/kernel-contribution.tex | 52 +++++-----------------
 2 files changed, 24 insertions(+), 40 deletions(-)

diff --git a/slides/first-slides/mylene-josserand.tex b/slides/first-slides/mylene-josserand.tex
new file mode 100644
index 0000000..7722b08
--- /dev/null
+++ b/slides/first-slides/mylene-josserand.tex
@@ -0,0 +1,12 @@
+\begin{frame}{Mylene Josserand}
+    \begin{itemize}
+	\item Embedded Linux engineer and trainer at Free Electrons since 2016
+	\item {\bf Linux kernel}: contributed support for Microcrystal RTCs
+	      and for NextThingCo's GR8 chip.
+	\item One of the authors of Free Electrons' {\bf Yocto Project / OpenEmbedded}
+	      training materials.
+	\item Living in {\bf Toulouse}, France
+	\item \code{mylene at free-electrons.com}
+    \end{itemize}
+    {\small \url{http://free-electrons.com/company/staff/mylene-josserand/}}
+\end{frame}
diff --git a/slides/kernel-contribution/kernel-contribution.tex b/slides/kernel-contribution/kernel-contribution.tex
index c5616d6..1302a80 100644
--- a/slides/kernel-contribution/kernel-contribution.tex
+++ b/slides/kernel-contribution/kernel-contribution.tex
@@ -1,47 +1,19 @@
 \subsection{Contributing to the Linux kernel}
 
 \begin{frame}
-  \frametitle{Solving Issues}
+  \frametitle{Getting help and reporting bugs}
   \begin{itemize}
-  \item If you face an issue, and it doesn't look specific to your
-    work but rather to the tools you are using, it is very likely that
-    someone else already faced it.
-  \item Search the Internet for similar error reports.
-  \item You have great chances of finding a solution or workaround, or
-    at least an explanation for your issue.
-  \item Otherwise, reporting the issue is up to you!
-  \end{itemize}
-\end{frame}
-
-\begin{frame}
-  \frametitle{Getting Help}
-  \begin{itemize}
-  \item If you have a support contract, ask your vendor.
-  \item Otherwise, don't hesitate to share your questions and issues
-    \begin{itemize}
-    \item Either contact the Linux mailing list for your architecture
-      (like linux-arm-kernel or linuxsh-dev...).
-    \item Or contact the mailing list for the subsystem you're dealing
-      with (linux-usb-devel, linux-mtd...). Don't ask the maintainer
-      directly!
-    \item Most mailing lists come with a FAQ page. Make sure you read
-      it before contacting the mailing list.
-    \item Useful IRC resources are available too
-      (for example on \url{http://kernelnewbies.org}).
-    \item Refrain from contacting the Linux Kernel mailing list,
-      unless you're an experienced developer and need advice.
-    \end{itemize}
-  \end{itemize}
-\end{frame}
-
-\begin{frame}
-  \frametitle{Reporting Linux Bugs}
-  \begin{itemize}
-  \item First make sure you're using the latest version
+  \item If you are using a custom kernel from a hardware vendor, contact
+        that company. The community will have less interest supporting
+        a custom kernel.
+  \item Otherwise, or if this doesn't work, try to reproduce the
+        issue on the latest version of the kernel. 
   \item Make sure you investigate the issue as much as you can: see
     \kerneldoctext{BUG-HUNTING}
   \item Check for previous bugs reports. Use web search engines,
     accessing public mailing list archives.
+  \item If you're the first to face the issue, it's very useful for
+    others to report it, even if you cannot investigate it further.
   \item If the subsystem you report a bug on has a mailing list, use
     it. Otherwise, contact the official maintainer (see the
     \kpath{MAINTAINERS} file). Always give as many useful details as
@@ -169,17 +141,18 @@ ARM: add support for xz kernel decompression
     \item \code{rm 00*.patch}
     \end{itemize}
   \item Have git generate patches corresponding to your branch
+    (assuming it is the current branch)
     \begin{itemize}
     \item If your branch is based on mainline
       \begin{itemize}
-      \item \code{git format-patch master..<your branch>}
+      \item \code{git format-patch master
       \end{itemize}
     \item If your branch is based on a remote branch
       \begin{itemize}
-      \item \code{git format-patch <remote>/<branch>..<your branch>}
+      \item \code{git format-patch <remote>/<branch>}
       \end{itemize}
     \end{itemize}
-  \item You can run a last check on all your patches (easy)
+  \item Make sure your patches pass \code{checkpatch.pl} checks:
     \begin{itemize}
     \item \code{scripts/checkpatch.pl --strict 00*.patch}
     \end{itemize}
@@ -246,4 +219,3 @@ linux-kernel at vger.kernel.org (open list)
   \end{itemize}
 \end{frame}
 
-