lkmp:lkmp_required_contributions
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
lkmp:lkmp_required_contributions [2019/10/02 23:34] ShuahKhanLF |
lkmp:lkmp_required_contributions [2021/01/20 17:55] (current) ShuahKhanLF |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Linux Kernel Mentorship Program Required Contributions ====== | ====== Linux Kernel Mentorship Program Required Contributions ====== | ||
| - | 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. | + | 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. |
| - | **Updates in progress for Spring program - Applications open on Oct 28th 2019. Stay tuned for announcements on the IRC channel.** | + | **Updates in progress for Spring program - Applications open on Oct 28th 2019. Wait for this page to be updated and stay tuned for announcements on the IRC channel.** |
| ==== Participate in Stable release process ==== | ==== Participate in Stable release process ==== | ||
| Line 19: | Line 19: | ||
| Find 2 to 3 [[https://syzkaller.appspot.com/syzbot|Syzbot]] null pointer deference and WARN bug reports which include reproducer to analyze. As an example this report [[https://syzkaller.appspot.com/bug?id=163388d1fb80146cd3ba22a11a5a1995c3eaaafe|[upstream] WARNING in dma_buf_vunmap]] includes reproducers. | Find 2 to 3 [[https://syzkaller.appspot.com/syzbot|Syzbot]] null pointer deference and WARN bug reports which include reproducer to analyze. As an example this report [[https://syzkaller.appspot.com/bug?id=163388d1fb80146cd3ba22a11a5a1995c3eaaafe|[upstream] WARNING in dma_buf_vunmap]] includes reproducers. | ||
| - | * Run reproducer to see if you can reproduce the problem | + | * Run the reproducer to see if you can reproduce the problem. |
| * Look at the crash report and walk through sources for a possible cause. | * 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 [[skhan@linuxfoundation.org| Shuah Khan]] and linux-kernel-mentees mailing list. | * Write-up a short report for each of the bugs you analyzed and share them with [[skhan@linuxfoundation.org| Shuah Khan]] and linux-kernel-mentees mailing list. | ||
| - | ==== Documentation tasks ==== | + | ==== Documentation tasks (Optional) ==== |
| Convert two .txt files to ReST format. You will find the tasks listed in [[lkmp:lkmp_task_list|Linux Kernel Task List]] | Convert two .txt files to ReST format. You will find the tasks listed in [[lkmp:lkmp_task_list|Linux Kernel Task List]] | ||
| - | ==== Kernel Tasks ==== | + | ==== Kernel Tasks (Optional) ==== |
| - | Pick 2 kernel tasks from the [[lkmp:lkmp_task_list|Linux Kernel Task List]] and send patches to fix the issues. | + | Pick two kernel tasks from the [[lkmp:lkmp_task_list|Linux Kernel Task List]] and send patches to fix the issues. |
| - | ==== Staging tree coding style cleanups (Optional learning task practice patch process) ==== | + | ==== Staging tree coding style cleanups (Learning task practice patch process) ==== |
| - | 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. | + | The 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 error fixing (Optional learning task practice patch process) ==== | + | ==== Static code analysis error fixing (Learning task practice patch process) ==== |
| - | 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 [[https://www.kernel.org/doc/html/latest/dev-tools/sparse.html|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. | + | Static code analysis is the process of detecting errors and flaws in the source code. The Linux kernel Makefile can be invoked with options to enable to run the [[https://www.kernel.org/doc/html/latest/dev-tools/sparse.html|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. |
lkmp/lkmp_required_contributions.1570059259.txt.gz · Last modified: 2019/10/02 23:34 by ShuahKhanLF
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
