blob: e2c9ffc682c520c0a91036372bcdc8d707c2a78a [file] [log] [blame]
Andrew Scullb4b6d4a2019-01-02 15:54:55 +00001.. 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
David Brazdil0f672f62019-12-10 10:32:29 +000022 license-rules
Andrew Scullb4b6d4a2019-01-02 15:54:55 +000023 howto
24 code-of-conduct
25 code-of-conduct-interpretation
26 development-process
27 submitting-patches
David Brazdil0f672f62019-12-10 10:32:29 +000028 programming-language
Andrew Scullb4b6d4a2019-01-02 15:54:55 +000029 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
David Brazdil0f672f62019-12-10 10:32:29 +000047 deprecated
48 embargoed-hardware-issues
Andrew Scullb4b6d4a2019-01-02 15:54:55 +000049
50These are some overall technical guides that have been put here for now for
51lack of a better place.
52
53.. toctree::
54 :maxdepth: 1
55
56 applying-patches
57 adding-syscalls
58 magic-number
59 volatile-considered-harmful
60 clang-format
61
62.. only:: subproject and html
63
64 Indices
65 =======
66
67 * :ref:`genindex`