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