1.. raw:: latex 2 3 \renewcommand\thesection* 4 \renewcommand\thesubsection* 5 6.. _process_index: 7 8============================================= 9Working with the kernel development community 10============================================= 11 12So you want to be a Linux kernel developer? Welcome! While there is a lot 13to be learned about the kernel in a technical sense, it is also important 14to learn about how our community works. Reading these documents will make 15it much easier for you to get your changes merged with a minimum of 16trouble. 17 18Below are the essential guides that every developer should read. 19 20.. toctree:: 21 :maxdepth: 1 22 23 license-rules 24 howto 25 code-of-conduct 26 code-of-conduct-interpretation 27 development-process 28 submitting-patches 29 handling-regressions 30 programming-language 31 coding-style 32 maintainer-handbooks 33 maintainer-pgp-guide 34 email-clients 35 kernel-enforcement-statement 36 kernel-driver-statement 37 38Other guides to the community that are of interest to most developers are: 39 40.. toctree:: 41 :maxdepth: 1 42 43 changes 44 stable-api-nonsense 45 management-style 46 stable-kernel-rules 47 submit-checklist 48 kernel-docs 49 deprecated 50 embargoed-hardware-issues 51 maintainers 52 researcher-guidelines 53 54These are some overall technical guides that have been put here for now for 55lack of a better place. 56 57.. toctree:: 58 :maxdepth: 1 59 60 applying-patches 61 adding-syscalls 62 magic-number 63 volatile-considered-harmful 64 botching-up-ioctls 65 clang-format 66 ../riscv/patch-acceptance 67 ../core-api/unaligned-memory-access 68 69.. only:: subproject and html 70 71 Indices 72 ======= 73 74 * :ref:`genindex` 75