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