blob: 61e43cc3ed171e2371b6372609533dc16fc9b057 [file] [log] [blame]
rjw1f884582022-01-06 17:20:42 +08001.. 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 howto
23 code-of-conflict
24 development-process
25 submitting-patches
26 coding-style
27 email-clients
28 kernel-enforcement-statement
29
30Other guides to the community that are of interest to most developers are:
31
32.. toctree::
33 :maxdepth: 1
34
35 changes
36 submitting-drivers
37 stable-api-nonsense
38 management-style
39 stable-kernel-rules
40 submit-checklist
41 kernel-docs
42
43These are some overall technical guides that have been put here for now for
44lack of a better place.
45
46.. toctree::
47 :maxdepth: 1
48
49 applying-patches
50 adding-syscalls
51 magic-number
52 volatile-considered-harmful
53
54.. only:: subproject and html
55
56 Indices
57 =======
58
59 * :ref:`genindex`