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