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-handbooks
31   maintainer-pgp-guide
32   email-clients
33   kernel-enforcement-statement
34   kernel-driver-statement
35
36Other guides to the community that are of interest to most developers are:
37
38.. toctree::
39   :maxdepth: 1
40
41   changes
42   submitting-drivers
43   stable-api-nonsense
44   management-style
45   stable-kernel-rules
46   submit-checklist
47   kernel-docs
48   deprecated
49   embargoed-hardware-issues
50   maintainers
51
52These are some overall technical guides that have been put here for now for
53lack of a better place.
54
55.. toctree::
56   :maxdepth: 1
57
58   applying-patches
59   adding-syscalls
60   magic-number
61   volatile-considered-harmful
62   botching-up-ioctls
63   clang-format
64   ../riscv/patch-acceptance
65   ../core-api/unaligned-memory-access
66
67.. only::  subproject and html
68
69   Indices
70   =======
71
72   * :ref:`genindex`
73