The required contributions are designed to enhance the mentorship experience by participating in the kernel release process. Please note that quality of patches is what will add value, not the quantity. If one candidate has 10 white space patches, and another has fewer more substantial patches, substantial work carries more weight.

Participating in the kernel release process will help understand how it works and how fixes flow from the mainline kernel into stable releases.

• Subscribe to Stable release mailing list
• Assist stable release maintainer(s)
• Boot test at least 2 or 3 stable releases during the 6 week application process and report results.

What do you do when kernel doesn't boot or kernel is crashing or driver isn't working the way it should? It is time to debug the kernel. This is intended to be a self study on learning to hunt bugs, bisecting a bug, learn about debug configuration options in the kernel config file, and how to use Dynamic debugging.

Find 2 to 3 [upstream] WARNING in dma_buf_vunmap includes reproducers.

• Run reproducer to see if you can reproduce the problem
• Look at the crash report and walk through sources for a possible cause.
• Write-up a short report for each of the bugs you analyzed and share them with Shuah Khan and linux-kernel-mentees mailing list.

Staging tree is a good place to start to learn the kernel development process and getting your patches into the mainline. Pick a staging area driver and run checkpatch.pl on a file. Fix coding style problems if any.

Static code analysis is the process of detecting errors and flaws in the source code. Linux kernel Makefile can be invoked with options to enable to run Sparse source code checker on all source file or only the re-compiled files. Compile kernel with source code checker enabled and find errors and fix as needed.