Greg Kroah-Hartman
598cf27219
Link: https://lore.kernel.org/r/20260217200002.683975158@linuxfoundation.org Tested-by: Florian Fainelli <florian.fainelli@broadcom.com> Tested-by: Takeshi Ogasawara <takeshi.ogasawara@futuring-girl.com> Tested-by: Peter Schneider <pschneider1968@googlemail.com> Tested-by: Jon Hunter <jonathanh@nvidia.com> Tested-by: Salvatore Bonaccorso <carnil@debian.org> Tested-by: Brett A C Sheffield <bacs@librecast.net> Tested-by: Mark Brown <broonie@kernel.org> Tested-by: Luna Jernberg <droidbittin@gmail.com> Tested-by: Ronald Warsow <rwarsow@gmx.de> Tested-by: Justin M. Forbes <jforbes@fedoraproject.org> Tested-by: Ron Economos <re@w6rz.net> Tested-by: Miguel Ojeda <ojeda@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
28 lines
821 B
ReStructuredText
28 lines
821 B
ReStructuredText
.. _development_process_main:
|
|
|
|
A guide to the Kernel Development Process
|
|
=========================================
|
|
|
|
The purpose of this document is to help developers (and their managers)
|
|
work with the development community with a minimum of frustration. It is
|
|
an attempt to document how this community works in a way which is
|
|
accessible to those who are not intimately familiar with Linux kernel
|
|
development (or, indeed, free software development in general). While
|
|
there is some technical material here, this is very much a process-oriented
|
|
discussion which does not require a deep knowledge of kernel programming to
|
|
understand.
|
|
|
|
.. toctree::
|
|
:caption: Contents
|
|
:numbered:
|
|
:maxdepth: 2
|
|
|
|
1.Intro
|
|
2.Process
|
|
3.Early-stage
|
|
4.Coding
|
|
5.Posting
|
|
6.Followthrough
|
|
7.AdvancedTopics
|
|
8.Conclusion
|