€•G      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ%/translations/zh_CN/process/2.Process”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ%/translations/zh_TW/process/2.Process”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ%/translations/it_IT/process/2.Process”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ%/translations/ja_JP/process/2.Process”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ%/translations/ko_KR/process/2.Process”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ%/translations/sp_SP/process/2.Process”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒtarget”“”)”}”(hŒ.. _development_process:”h]”h}”(h]”h ]”h"]”h$]”h&]”Œrefid”Œdevelopment-process”uh1h¡h KhhhžhhŸŒ?/var/lib/git/docbuild/linux/Documentation/process/2.Process.rst”ubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ!How the development process works”h]”hŒ!How the development process works”…””}”(hh·hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhh²hžhhŸh¯h KubhŒ	paragraph”“”)”}”(hX³  Linux kernel development in the early 1990's was a pretty loose affair,
with relatively small numbers of users and developers involved.  With a
user base in the millions and with some 2,000 developers involved over the
course of one year, the kernel has since had to evolve a number of
processes to keep development happening smoothly.  A solid understanding of
how the process works is required in order to be an effective part of it.”h]”hXµ  Linux kernel development in the early 1990â€™s was a pretty loose affair,
with relatively small numbers of users and developers involved.  With a
user base in the millions and with some 2,000 developers involved over the
course of one year, the kernel has since had to evolve a number of
processes to keep development happening smoothly.  A solid understanding of
how the process works is required in order to be an effective part of it.”…””}”(hhÇhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Khh²hžhubh±)”}”(hhh]”(h¶)”}”(hŒThe big picture”h]”hŒThe big picture”…””}”(hhØhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhhÕhžhhŸh¯h KubhÆ)”}”(hŒ±The kernel developers use a loosely time-based release process, with a new
major kernel release happening every two or three months.  The recent
release history looks like this:”h]”hŒ±The kernel developers use a loosely time-based release process, with a new
major kernel release happening every two or three months.  The recent
release history looks like this:”…””}”(hhæhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KhhÕhžhubhŒblock_quote”“”)”}”(hŒÀ======  =================
5.0     March 3, 2019
5.1     May 5, 2019
5.2     July 7, 2019
5.3     September 15, 2019
5.4     November 24, 2019
5.5     January 6, 2020
======  =================
”h]”hŒtable”“”)”}”(hhh]”hŒtgroup”“”)”}”(hhh]”(hŒcolspec”“”)”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1j  hj  ubj  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1j  hj  ubhŒtbody”“”)”}”(hhh]”(hŒrow”“”)”}”(hhh]”(hŒentry”“”)”}”(hhh]”hÆ)”}”(hŒ5.0”h]”hŒ5.0”…””}”(hj)  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Khj&  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj!  ubj%  )”}”(hhh]”hÆ)”}”(hŒMarch 3, 2019”h]”hŒMarch 3, 2019”…””}”(hj@  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Khj=  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj!  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒ5.1”h]”hŒ5.1”…””}”(hj`  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Khj]  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjZ  ubj%  )”}”(hhh]”hÆ)”}”(hŒMay 5, 2019”h]”hŒMay 5, 2019”…””}”(hjw  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Khjt  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjZ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒ5.2”h]”hŒ5.2”…””}”(hj—  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Khj”  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj‘  ubj%  )”}”(hhh]”hÆ)”}”(hŒJuly 7, 2019”h]”hŒJuly 7, 2019”…””}”(hj®  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Khj«  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj‘  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒ5.3”h]”hŒ5.3”…””}”(hjÎ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KhjË  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjÈ  ubj%  )”}”(hhh]”hÆ)”}”(hŒSeptember 15, 2019”h]”hŒSeptember 15, 2019”…””}”(hjå  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Khjâ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjÈ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒ5.4”h]”hŒ5.4”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjÿ  ubj%  )”}”(hhh]”hÆ)”}”(hŒNovember 24, 2019”h]”hŒNovember 24, 2019”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjÿ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒ5.5”h]”hŒ5.5”…””}”(hj<  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Khj9  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj6  ubj%  )”}”(hhh]”hÆ)”}”(hŒJanuary 6, 2020”h]”hŒJanuary 6, 2020”…””}”(hjS  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KhjP  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj6  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”Œcols”Kuh1hÿhhüubah}”(h]”h ]”h"]”h$]”h&]”uh1húhhöubah}”(h]”h ]”h"]”h$]”h&]”uh1hôhŸh¯h KhhÕhžhubhÆ)”}”(hX_  Every 5.x release is a major kernel release with new features, internal
API changes, and more.  A typical release can contain about 13,000
changesets with changes to several hundred thousand lines of code.  5.x is
the leading edge of Linux kernel development; the kernel uses a
rolling development model which is continually integrating major changes.”h]”hX_  Every 5.x release is a major kernel release with new features, internal
API changes, and more.  A typical release can contain about 13,000
changesets with changes to several hundred thousand lines of code.  5.x is
the leading edge of Linux kernel development; the kernel uses a
rolling development model which is continually integrating major changes.”…””}”(hj†  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KhhÕhžhubhÆ)”}”(hX  A relatively straightforward discipline is followed with regard to the
merging of patches for each release.  At the beginning of each development
cycle, the "merge window" is said to be open.  At that time, code which is
deemed to be sufficiently stable (and which is accepted by the development
community) is merged into the mainline kernel.  The bulk of changes for a
new development cycle (and all of the major changes) will be merged during
this time, at a rate approaching 1,000 changes ("patches," or "changesets")
per day.”h]”hX  A relatively straightforward discipline is followed with regard to the
merging of patches for each release.  At the beginning of each development
cycle, the â€œmerge windowâ€ is said to be open.  At that time, code which is
deemed to be sufficiently stable (and which is accepted by the development
community) is merged into the mainline kernel.  The bulk of changes for a
new development cycle (and all of the major changes) will be merged during
this time, at a rate approaching 1,000 changes (â€œpatches,â€ or â€œchangesetsâ€)
per day.”…””}”(hj”  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K#hhÕhžhubhÆ)”}”(hŒì(As an aside, it is worth noting that the changes integrated during the
merge window do not come out of thin air; they have been collected, tested,
and staged ahead of time.  How that process works will be described in
detail later on).”h]”hŒì(As an aside, it is worth noting that the changes integrated during the
merge window do not come out of thin air; they have been collected, tested,
and staged ahead of time.  How that process works will be described in
detail later on).”…””}”(hj¢  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K,hhÕhžhubhÆ)”}”(hXÃ  The merge window lasts for approximately two weeks.  At the end of this
time, Linus Torvalds will declare that the window is closed and release the
first of the "rc" kernels.  For the kernel which is destined to be 5.6,
for example, the release which happens at the end of the merge window will
be called 5.6-rc1.  The -rc1 release is the signal that the time to
merge new features has passed, and that the time to stabilize the next
kernel has begun.”h]”hXÇ  The merge window lasts for approximately two weeks.  At the end of this
time, Linus Torvalds will declare that the window is closed and release the
first of the â€œrcâ€ kernels.  For the kernel which is destined to be 5.6,
for example, the release which happens at the end of the merge window will
be called 5.6-rc1.  The -rc1 release is the signal that the time to
merge new features has passed, and that the time to stabilize the next
kernel has begun.”…””}”(hj°  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K1hhÕhžhubhÆ)”}”(hX`  Over the next six to ten weeks, only patches which fix problems should be
submitted to the mainline.  On occasion a more significant change will be
allowed, but such occasions are rare; developers who try to merge new
features outside of the merge window tend to get an unfriendly reception.
As a general rule, if you miss the merge window for a given feature, the
best thing to do is to wait for the next development cycle.  (An occasional
exception is made for drivers for previously-unsupported hardware; if they
touch no in-tree code, they cannot cause regressions and should be safe to
add at any time).”h]”hX`  Over the next six to ten weeks, only patches which fix problems should be
submitted to the mainline.  On occasion a more significant change will be
allowed, but such occasions are rare; developers who try to merge new
features outside of the merge window tend to get an unfriendly reception.
As a general rule, if you miss the merge window for a given feature, the
best thing to do is to wait for the next development cycle.  (An occasional
exception is made for drivers for previously-unsupported hardware; if they
touch no in-tree code, they cannot cause regressions and should be safe to
add at any time).”…””}”(hj¾  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K9hhÕhžhubhÆ)”}”(hXL  As fixes make their way into the mainline, the patch rate will slow over
time.  Linus releases new -rc kernels about once a week; a normal series
will get up to somewhere between -rc6 and -rc9 before the kernel is
considered to be sufficiently stable and the final release is made.
At that point the whole process starts over again.”h]”hXL  As fixes make their way into the mainline, the patch rate will slow over
time.  Linus releases new -rc kernels about once a week; a normal series
will get up to somewhere between -rc6 and -rc9 before the kernel is
considered to be sufficiently stable and the final release is made.
At that point the whole process starts over again.”…””}”(hjÌ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KChhÕhžhubhÆ)”}”(hŒNAs an example, here is how the 5.4 development cycle went (all dates in
2019):”h]”hŒNAs an example, here is how the 5.4 development cycle went (all dates in
2019):”…””}”(hjÚ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KIhhÕhžhubhõ)”}”(hX{  ==============  ===============================
September 15    5.3 stable release
September 30    5.4-rc1, merge window closes
October 6       5.4-rc2
October 13      5.4-rc3
October 20      5.4-rc4
October 27      5.4-rc5
November 3      5.4-rc6
November 10     5.4-rc7
November 17     5.4-rc8
November 24     5.4 stable release
==============  ===============================
”h]”hû)”}”(hhh]”j   )”}”(hhh]”(j  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1j  hjï  ubj  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1j  hjï  ubj  )”}”(hhh]”(j   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒSeptember 15”h]”hŒSeptember 15”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KMhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj	  ubj%  )”}”(hhh]”hÆ)”}”(hŒ5.3 stable release”h]”hŒ5.3 stable release”…””}”(hj&  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KMhj#  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒSeptember 30”h]”hŒSeptember 30”…””}”(hjF  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KNhjC  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj@  ubj%  )”}”(hhh]”hÆ)”}”(hŒ5.4-rc1, merge window closes”h]”hŒ5.4-rc1, merge window closes”…””}”(hj]  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KNhjZ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj@  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒ	October 6”h]”hŒ	October 6”…””}”(hj}  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KOhjz  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjw  ubj%  )”}”(hhh]”hÆ)”}”(hŒ5.4-rc2”h]”hŒ5.4-rc2”…””}”(hj”  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KOhj‘  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjw  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒ
October 13”h]”hŒ
October 13”…””}”(hj´  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KPhj±  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj®  ubj%  )”}”(hhh]”hÆ)”}”(hŒ5.4-rc3”h]”hŒ5.4-rc3”…””}”(hjË  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KPhjÈ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj®  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒ
October 20”h]”hŒ
October 20”…””}”(hjë  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KQhjè  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjå  ubj%  )”}”(hhh]”hÆ)”}”(hŒ5.4-rc4”h]”hŒ5.4-rc4”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KQhjÿ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjå  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒ
October 27”h]”hŒ
October 27”…””}”(hj"  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KRhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj  ubj%  )”}”(hhh]”hÆ)”}”(hŒ5.4-rc5”h]”hŒ5.4-rc5”…””}”(hj9  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KRhj6  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒ
November 3”h]”hŒ
November 3”…””}”(hjY  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KShjV  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjS  ubj%  )”}”(hhh]”hÆ)”}”(hŒ5.4-rc6”h]”hŒ5.4-rc6”…””}”(hjp  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KShjm  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjS  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒNovember 10”h]”hŒNovember 10”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KThj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjŠ  ubj%  )”}”(hhh]”hÆ)”}”(hŒ5.4-rc7”h]”hŒ5.4-rc7”…””}”(hj§  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KThj¤  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjŠ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒNovember 17”h]”hŒNovember 17”…””}”(hjÇ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KUhjÄ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjÁ  ubj%  )”}”(hhh]”hÆ)”}”(hŒ5.4-rc8”h]”hŒ5.4-rc8”…””}”(hjÞ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KUhjÛ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjÁ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒNovember 24”h]”hŒNovember 24”…””}”(hjþ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KVhjû  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjø  ubj%  )”}”(hhh]”hÆ)”}”(hŒ5.4 stable release”h]”hŒ5.4 stable release”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KVhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjø  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjï  ubeh}”(h]”h ]”h"]”h$]”h&]”Œcols”Kuh1hÿhjì  ubah}”(h]”h ]”h"]”h$]”h&]”uh1húhjè  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hôhŸh¯h KLhhÕhžhubhÆ)”}”(hX½  How do the developers decide when to close the development cycle and create
the stable release?  The most significant metric used is the list of
regressions from previous releases.  No bugs are welcome, but those which
break systems which worked in the past are considered to be especially
serious.  For this reason, patches which cause regressions are looked upon
unfavorably and are quite likely to be reverted during the stabilization
period.”h]”hX½  How do the developers decide when to close the development cycle and create
the stable release?  The most significant metric used is the list of
regressions from previous releases.  No bugs are welcome, but those which
break systems which worked in the past are considered to be especially
serious.  For this reason, patches which cause regressions are looked upon
unfavorably and are quite likely to be reverted during the stabilization
period.”…””}”(hjH  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KYhhÕhžhubhÆ)”}”(hX  The developers' goal is to fix all known regressions before the stable
release is made.  In the real world, this kind of perfection is hard to
achieve; there are just too many variables in a project of this size.
There comes a point where delaying the final release just makes the problem
worse; the pile of changes waiting for the next merge window will grow
larger, creating even more regressions the next time around.  So most 5.x
kernels go out with a handful of known regressions though, hopefully, none
of them are serious.”h]”hX  The developersâ€™ goal is to fix all known regressions before the stable
release is made.  In the real world, this kind of perfection is hard to
achieve; there are just too many variables in a project of this size.
There comes a point where delaying the final release just makes the problem
worse; the pile of changes waiting for the next merge window will grow
larger, creating even more regressions the next time around.  So most 5.x
kernels go out with a handful of known regressions though, hopefully, none
of them are serious.”…””}”(hjV  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KahhÕhžhubhÆ)”}”(hXD  Once a stable release is made, its ongoing maintenance is passed off to the
"stable team," currently Greg Kroah-Hartman. The stable team will release
occasional updates to the stable release using the 5.x.y numbering scheme.
To be considered for an update release, a patch must (1) fix a significant
bug, and (2) already be merged into the mainline for the next development
kernel. Kernels will typically receive stable updates for a little more
than one development cycle past their initial release. So, for example, the
5.2 kernel's history looked like this (all dates in 2019):”h]”hXJ  Once a stable release is made, its ongoing maintenance is passed off to the
â€œstable team,â€ currently Greg Kroah-Hartman. The stable team will release
occasional updates to the stable release using the 5.x.y numbering scheme.
To be considered for an update release, a patch must (1) fix a significant
bug, and (2) already be merged into the mainline for the next development
kernel. Kernels will typically receive stable updates for a little more
than one development cycle past their initial release. So, for example, the
5.2 kernelâ€™s history looked like this (all dates in 2019):”…””}”(hjd  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KjhhÕhžhubhõ)”}”(hX  ==============  ===============================
July 7          5.2 stable release
July 14         5.2.1
July 21         5.2.2
July 26         5.2.3
July 28         5.2.4
July 31         5.2.5
...             ...
October 11      5.2.21
==============  ===============================
”h]”hû)”}”(hhh]”j   )”}”(hhh]”(j  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1j  hjy  ubj  )”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1j  hjy  ubj  )”}”(hhh]”(j   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒJuly 7”h]”hŒJuly 7”…””}”(hj™  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Kthj–  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj“  ubj%  )”}”(hhh]”hÆ)”}”(hŒ5.2 stable release”h]”hŒ5.2 stable release”…””}”(hj°  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Kthj­  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj“  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒJuly 14”h]”hŒJuly 14”…””}”(hjÐ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KuhjÍ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjÊ  ubj%  )”}”(hhh]”hÆ)”}”(hŒ5.2.1”h]”hŒ5.2.1”…””}”(hjç  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Kuhjä  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjÊ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒJuly 21”h]”hŒJuly 21”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Kvhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj  ubj%  )”}”(hhh]”hÆ)”}”(hŒ5.2.2”h]”hŒ5.2.2”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Kvhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒJuly 26”h]”hŒJuly 26”…””}”(hj>  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Kwhj;  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj8  ubj%  )”}”(hhh]”hÆ)”}”(hŒ5.2.3”h]”hŒ5.2.3”…””}”(hjU  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KwhjR  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj8  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒJuly 28”h]”hŒJuly 28”…””}”(hju  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Kxhjr  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjo  ubj%  )”}”(hhh]”hÆ)”}”(hŒ5.2.4”h]”hŒ5.2.4”…””}”(hjŒ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Kxhj‰  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjo  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒJuly 31”h]”hŒJuly 31”…””}”(hj¬  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Kyhj©  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj¦  ubj%  )”}”(hhh]”hÆ)”}”(hŒ5.2.5”h]”hŒ5.2.5”…””}”(hjÃ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KyhjÀ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj¦  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒ...”h]”hŒ...”…””}”(hjã  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Kzhjà  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjÝ  ubj%  )”}”(hhh]”hÆ)”}”(hŒ...”h]”hŒ...”…””}”(hjú  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Kzhj÷  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hjÝ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubj   )”}”(hhh]”(j%  )”}”(hhh]”hÆ)”}”(hŒ
October 11”h]”hŒ
October 11”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K{hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj  ubj%  )”}”(hhh]”hÆ)”}”(hŒ5.2.21”h]”hŒ5.2.21”…””}”(hj1  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K{hj.  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j$  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjy  ubeh}”(h]”h ]”h"]”h$]”h&]”Œcols”Kuh1hÿhjv  ubah}”(h]”h ]”h"]”h$]”h&]”uh1húhjr  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hôhŸh¯h KshhÕhžhubhÆ)”}”(hŒ65.2.21 was the final stable update of the 5.2 release.”h]”hŒ65.2.21 was the final stable update of the 5.2 release.”…””}”(hjd  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K~hhÕhžhubhÆ)”}”(hŒËSome kernels are designated "long term" kernels; they will receive support
for a longer period.  Please refer to the following link for the list of active
long term kernel versions and their maintainers:”h]”hŒÏSome kernels are designated â€œlong termâ€ kernels; they will receive support
for a longer period.  Please refer to the following link for the list of active
long term kernel versions and their maintainers:”…””}”(hjr  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K€hhÕhžhubhõ)”}”(hŒ.https://www.kernel.org/category/releases.html
”h]”hÆ)”}”(hŒ-https://www.kernel.org/category/releases.html”h]”hŒ	reference”“”)”}”(hj†  h]”hŒ-https://www.kernel.org/category/releases.html”…””}”(hjŠ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j†  uh1jˆ  hj„  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K„hj€  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hôhŸh¯h K„hhÕhžhubhÆ)”}”(hŒÜThe selection of a kernel for long-term support is purely a matter of a
maintainer having the need and the time to maintain that release.  There
are no known plans for long-term support for any specific upcoming
release.”h]”hŒÜThe selection of a kernel for long-term support is purely a matter of a
maintainer having the need and the time to maintain that release.  There
are no known plans for long-term support for any specific upcoming
release.”…””}”(hj¤  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K†hhÕhžhubeh}”(h]”Œthe-big-picture”ah ]”h"]”Œthe big picture”ah$]”h&]”uh1h°hh²hžhhŸh¯h Kubh±)”}”(hhh]”(h¶)”}”(hŒThe lifecycle of a patch”h]”hŒThe lifecycle of a patch”…””}”(hj½  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhjº  hžhhŸh¯h KubhÆ)”}”(hX  Patches do not go directly from the developer's keyboard into the mainline
kernel.  There is, instead, a somewhat involved (if somewhat informal)
process designed to ensure that each patch is reviewed for quality and that
each patch implements a change which is desirable to have in the mainline.
This process can happen quickly for minor fixes, or, in the case of large
and controversial changes, go on for years.  Much developer frustration
comes from a lack of understanding of this process or from attempts to
circumvent it.”h]”hX  Patches do not go directly from the developerâ€™s keyboard into the mainline
kernel.  There is, instead, a somewhat involved (if somewhat informal)
process designed to ensure that each patch is reviewed for quality and that
each patch implements a change which is desirable to have in the mainline.
This process can happen quickly for minor fixes, or, in the case of large
and controversial changes, go on for years.  Much developer frustration
comes from a lack of understanding of this process or from attempts to
circumvent it.”…””}”(hjË  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Khjº  hžhubhÆ)”}”(hX  In the hopes of reducing that frustration, this document will describe how
a patch gets into the kernel.  What follows below is an introduction which
describes the process in a somewhat idealized way.  A much more detailed
treatment will come in later sections.”h]”hX  In the hopes of reducing that frustration, this document will describe how
a patch gets into the kernel.  What follows below is an introduction which
describes the process in a somewhat idealized way.  A much more detailed
treatment will come in later sections.”…””}”(hjÙ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K˜hjº  hžhubhÆ)”}”(hŒ4The stages that a patch goes through are, generally:”h]”hŒ4The stages that a patch goes through are, generally:”…””}”(hjç  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Khjº  hžhubhõ)”}”(hX2  - Design.  This is where the real requirements for the patch - and the way
  those requirements will be met - are laid out.  Design work is often
  done without involving the community, but it is better to do this work
  in the open if at all possible; it can save a lot of time redesigning
  things later.

- Early review.  Patches are posted to the relevant mailing list, and
  developers on that list reply with any comments they may have.  This
  process should turn up any major problems with a patch if all goes
  well.

- Wider review.  When the patch is getting close to ready for mainline
  inclusion, it should be accepted by a relevant subsystem maintainer -
  though this acceptance is not a guarantee that the patch will make it
  all the way to the mainline.  The patch will show up in the maintainer's
  subsystem tree and into the -next trees (described below).  When the
  process works, this step leads to more extensive review of the patch and
  the discovery of any problems resulting from the integration of this
  patch with work being done by others.
”h]”hŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hX)  Design.  This is where the real requirements for the patch - and the way
those requirements will be met - are laid out.  Design work is often
done without involving the community, but it is better to do this work
in the open if at all possible; it can save a lot of time redesigning
things later.
”h]”hÆ)”}”(hX(  Design.  This is where the real requirements for the patch - and the way
those requirements will be met - are laid out.  Design work is often
done without involving the community, but it is better to do this work
in the open if at all possible; it can save a lot of time redesigning
things later.”h]”hX(  Design.  This is where the real requirements for the patch - and the way
those requirements will be met - are laid out.  Design work is often
done without involving the community, but it is better to do this work
in the open if at all possible; it can save a lot of time redesigning
things later.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KŸhj   ubah}”(h]”h ]”h"]”h$]”h&]”uh1jþ  hjû  ubjÿ  )”}”(hŒÒEarly review.  Patches are posted to the relevant mailing list, and
developers on that list reply with any comments they may have.  This
process should turn up any major problems with a patch if all goes
well.
”h]”hÆ)”}”(hŒÑEarly review.  Patches are posted to the relevant mailing list, and
developers on that list reply with any comments they may have.  This
process should turn up any major problems with a patch if all goes
well.”h]”hŒÑEarly review.  Patches are posted to the relevant mailing list, and
developers on that list reply with any comments they may have.  This
process should turn up any major problems with a patch if all goes
well.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K¥hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jþ  hjû  ubjÿ  )”}”(hX  Wider review.  When the patch is getting close to ready for mainline
inclusion, it should be accepted by a relevant subsystem maintainer -
though this acceptance is not a guarantee that the patch will make it
all the way to the mainline.  The patch will show up in the maintainer's
subsystem tree and into the -next trees (described below).  When the
process works, this step leads to more extensive review of the patch and
the discovery of any problems resulting from the integration of this
patch with work being done by others.
”h]”hÆ)”}”(hX  Wider review.  When the patch is getting close to ready for mainline
inclusion, it should be accepted by a relevant subsystem maintainer -
though this acceptance is not a guarantee that the patch will make it
all the way to the mainline.  The patch will show up in the maintainer's
subsystem tree and into the -next trees (described below).  When the
process works, this step leads to more extensive review of the patch and
the discovery of any problems resulting from the integration of this
patch with work being done by others.”h]”hX  Wider review.  When the patch is getting close to ready for mainline
inclusion, it should be accepted by a relevant subsystem maintainer -
though this acceptance is not a guarantee that the patch will make it
all the way to the mainline.  The patch will show up in the maintainerâ€™s
subsystem tree and into the -next trees (described below).  When the
process works, this step leads to more extensive review of the patch and
the discovery of any problems resulting from the integration of this
patch with work being done by others.”…””}”(hj4  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Kªhj0  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jþ  hjû  ubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1jù  hŸh¯h KŸhjõ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hôhŸh¯h KŸhjº  hžhubjú  )”}”(hhh]”jÿ  )”}”(hXý  Please note that most maintainers also have day jobs, so merging
your patch may not be their highest priority.  If your patch is
getting feedback about changes that are needed, you should either
make those changes or justify why they should not be made.  If your
patch has no review complaints but is not being merged by its
appropriate subsystem or driver maintainer, you should be persistent
in updating the patch to the current kernel so that it applies cleanly
and keep sending it for review and merging.
”h]”hÆ)”}”(hXü  Please note that most maintainers also have day jobs, so merging
your patch may not be their highest priority.  If your patch is
getting feedback about changes that are needed, you should either
make those changes or justify why they should not be made.  If your
patch has no review complaints but is not being merged by its
appropriate subsystem or driver maintainer, you should be persistent
in updating the patch to the current kernel so that it applies cleanly
and keep sending it for review and merging.”h]”hXü  Please note that most maintainers also have day jobs, so merging
your patch may not be their highest priority.  If your patch is
getting feedback about changes that are needed, you should either
make those changes or justify why they should not be made.  If your
patch has no review complaints but is not being merged by its
appropriate subsystem or driver maintainer, you should be persistent
in updating the patch to the current kernel so that it applies cleanly
and keep sending it for review and merging.”…””}”(hj]  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K³hjY  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jþ  hjV  hžhhŸh¯h Nubah}”(h]”h ]”h"]”h$]”h&]”jN  jO  uh1jù  hŸh¯h K³hjº  hžhubhõ)”}”(hX`  - Merging into the mainline.  Eventually, a successful patch will be
  merged into the mainline repository managed by Linus Torvalds.  More
  comments and/or problems may surface at this time; it is important that
  the developer be responsive to these and fix any issues which arise.

- Stable release.  The number of users potentially affected by the patch
  is now large, so, once again, new problems may arise.

- Long-term maintenance.  While it is certainly possible for a developer
  to forget about code after merging it, that sort of behavior tends to
  leave a poor impression in the development community.  Merging code
  eliminates some of the maintenance burden, in that others will fix
  problems caused by API changes.  But the original developer should
  continue to take responsibility for the code if it is to remain useful
  in the longer term.
”h]”jú  )”}”(hhh]”(jÿ  )”}”(hX  Merging into the mainline.  Eventually, a successful patch will be
merged into the mainline repository managed by Linus Torvalds.  More
comments and/or problems may surface at this time; it is important that
the developer be responsive to these and fix any issues which arise.
”h]”hÆ)”}”(hX  Merging into the mainline.  Eventually, a successful patch will be
merged into the mainline repository managed by Linus Torvalds.  More
comments and/or problems may surface at this time; it is important that
the developer be responsive to these and fix any issues which arise.”h]”hX  Merging into the mainline.  Eventually, a successful patch will be
merged into the mainline repository managed by Linus Torvalds.  More
comments and/or problems may surface at this time; it is important that
the developer be responsive to these and fix any issues which arise.”…””}”(hj‚  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K¼hj~  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jþ  hj{  ubjÿ  )”}”(hŒ}Stable release.  The number of users potentially affected by the patch
is now large, so, once again, new problems may arise.
”h]”hÆ)”}”(hŒ|Stable release.  The number of users potentially affected by the patch
is now large, so, once again, new problems may arise.”h]”hŒ|Stable release.  The number of users potentially affected by the patch
is now large, so, once again, new problems may arise.”…””}”(hjš  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KÁhj–  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jþ  hj{  ubjÿ  )”}”(hX²  Long-term maintenance.  While it is certainly possible for a developer
to forget about code after merging it, that sort of behavior tends to
leave a poor impression in the development community.  Merging code
eliminates some of the maintenance burden, in that others will fix
problems caused by API changes.  But the original developer should
continue to take responsibility for the code if it is to remain useful
in the longer term.
”h]”hÆ)”}”(hX±  Long-term maintenance.  While it is certainly possible for a developer
to forget about code after merging it, that sort of behavior tends to
leave a poor impression in the development community.  Merging code
eliminates some of the maintenance burden, in that others will fix
problems caused by API changes.  But the original developer should
continue to take responsibility for the code if it is to remain useful
in the longer term.”h]”hX±  Long-term maintenance.  While it is certainly possible for a developer
to forget about code after merging it, that sort of behavior tends to
leave a poor impression in the development community.  Merging code
eliminates some of the maintenance burden, in that others will fix
problems caused by API changes.  But the original developer should
continue to take responsibility for the code if it is to remain useful
in the longer term.”…””}”(hj²  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KÄhj®  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jþ  hj{  ubeh}”(h]”h ]”h"]”h$]”h&]”jN  jO  uh1jù  hŸh¯h K¼hjw  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hôhŸh¯h K¼hjº  hžhubhÆ)”}”(hŒáOne of the largest mistakes made by kernel developers (or their employers)
is to try to cut the process down to a single "merging into the mainline"
step.  This approach invariably leads to frustration for everybody
involved.”h]”hŒåOne of the largest mistakes made by kernel developers (or their employers)
is to try to cut the process down to a single â€œmerging into the mainlineâ€
step.  This approach invariably leads to frustration for everybody
involved.”…””}”(hjÒ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KÌhjº  hžhubeh}”(h]”Œthe-lifecycle-of-a-patch”ah ]”h"]”Œthe lifecycle of a patch”ah$]”h&]”uh1h°hh²hžhhŸh¯h Kubh±)”}”(hhh]”(h¶)”}”(hŒHow patches get into the Kernel”h]”hŒHow patches get into the Kernel”…””}”(hjë  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhjè  hžhhŸh¯h KÒubhÆ)”}”(hXû  There is exactly one person who can merge patches into the mainline kernel
repository: Linus Torvalds. But, for example, of the over 9,500 patches
which went into the 2.6.38 kernel, only 112 (around 1.3%) were directly
chosen by Linus himself. The kernel project has long since grown to a size
where no single developer could possibly inspect and select every patch
unassisted. The way the kernel developers have addressed this growth is
through the use of a lieutenant system built around a chain of trust.”h]”hXû  There is exactly one person who can merge patches into the mainline kernel
repository: Linus Torvalds. But, for example, of the over 9,500 patches
which went into the 2.6.38 kernel, only 112 (around 1.3%) were directly
chosen by Linus himself. The kernel project has long since grown to a size
where no single developer could possibly inspect and select every patch
unassisted. The way the kernel developers have addressed this growth is
through the use of a lieutenant system built around a chain of trust.”…””}”(hjù  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KÔhjè  hžhubhÆ)”}”(hXà  The kernel code base is logically broken down into a set of subsystems:
networking, specific architecture support, memory management, video
devices, etc.  Most subsystems have a designated maintainer, a developer
who has overall responsibility for the code within that subsystem.  These
subsystem maintainers are the gatekeepers (in a loose way) for the portion
of the kernel they manage; they are the ones who will (usually) accept a
patch for inclusion into the mainline kernel.”h]”hXà  The kernel code base is logically broken down into a set of subsystems:
networking, specific architecture support, memory management, video
devices, etc.  Most subsystems have a designated maintainer, a developer
who has overall responsibility for the code within that subsystem.  These
subsystem maintainers are the gatekeepers (in a loose way) for the portion
of the kernel they manage; they are the ones who will (usually) accept a
patch for inclusion into the mainline kernel.”…””}”(hj	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KÜhjè  hžhubhÆ)”}”(hX¬  Subsystem maintainers each manage their own version of the kernel source
tree, usually (but certainly not always) using the git source management
tool.  Tools like git (and related tools like quilt or mercurial) allow
maintainers to track a list of patches, including authorship information
and other metadata.  At any given time, the maintainer can identify which
patches in his or her repository are not found in the mainline.”h]”hX¬  Subsystem maintainers each manage their own version of the kernel source
tree, usually (but certainly not always) using the git source management
tool.  Tools like git (and related tools like quilt or mercurial) allow
maintainers to track a list of patches, including authorship information
and other metadata.  At any given time, the maintainer can identify which
patches in his or her repository are not found in the mainline.”…””}”(hj	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Kähjè  hžhubhÆ)”}”(hXù  When the merge window opens, top-level maintainers will ask Linus to "pull"
the patches they have selected for merging from their repositories.  If
Linus agrees, the stream of patches will flow up into his repository,
becoming part of the mainline kernel.  The amount of attention that Linus
pays to specific patches received in a pull operation varies.  It is clear
that, sometimes, he looks quite closely.  But, as a general rule, Linus
trusts the subsystem maintainers to not send bad patches upstream.”h]”hXý  When the merge window opens, top-level maintainers will ask Linus to â€œpullâ€
the patches they have selected for merging from their repositories.  If
Linus agrees, the stream of patches will flow up into his repository,
becoming part of the mainline kernel.  The amount of attention that Linus
pays to specific patches received in a pull operation varies.  It is clear
that, sometimes, he looks quite closely.  But, as a general rule, Linus
trusts the subsystem maintainers to not send bad patches upstream.”…””}”(hj#	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Këhjè  hžhubhÆ)”}”(hX½  Subsystem maintainers, in turn, can pull patches from other maintainers.
For example, the networking tree is built from patches which accumulated
first in trees dedicated to network device drivers, wireless networking,
etc.  This chain of repositories can be arbitrarily long, though it rarely
exceeds two or three links.  Since each maintainer in the chain trusts
those managing lower-level trees, this process is known as the "chain of
trust."”h]”hXÁ  Subsystem maintainers, in turn, can pull patches from other maintainers.
For example, the networking tree is built from patches which accumulated
first in trees dedicated to network device drivers, wireless networking,
etc.  This chain of repositories can be arbitrarily long, though it rarely
exceeds two or three links.  Since each maintainer in the chain trusts
those managing lower-level trees, this process is known as the â€œchain of
trust.â€”…””}”(hj1	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Kóhjè  hžhubhÆ)”}”(hŒ°Clearly, in a system like this, getting patches into the kernel depends on
finding the right maintainer.  Sending patches directly to Linus is not
normally the right way to go.”h]”hŒ°Clearly, in a system like this, getting patches into the kernel depends on
finding the right maintainer.  Sending patches directly to Linus is not
normally the right way to go.”…””}”(hj?	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Kûhjè  hžhubeh}”(h]”Œhow-patches-get-into-the-kernel”ah ]”h"]”Œhow patches get into the kernel”ah$]”h&]”uh1h°hh²hžhhŸh¯h KÒubh±)”}”(hhh]”(h¶)”}”(hŒ
Next trees”h]”hŒ
Next trees”…””}”(hjX	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhjU	  hžhhŸh¯h MubhÆ)”}”(hXß  The chain of subsystem trees guides the flow of patches into the kernel,
but it also raises an interesting question: what if somebody wants to look
at all of the patches which are being prepared for the next merge window?
Developers will be interested in what other changes are pending to see
whether there are any conflicts to worry about; a patch which changes a
core kernel function prototype, for example, will conflict with any other
patches which use the older form of that function.  Reviewers and testers
want access to the changes in their integrated form before all of those
changes land in the mainline kernel.  One could pull changes from all of
the interesting subsystem trees, but that would be a big and error-prone
job.”h]”hXß  The chain of subsystem trees guides the flow of patches into the kernel,
but it also raises an interesting question: what if somebody wants to look
at all of the patches which are being prepared for the next merge window?
Developers will be interested in what other changes are pending to see
whether there are any conflicts to worry about; a patch which changes a
core kernel function prototype, for example, will conflict with any other
patches which use the older form of that function.  Reviewers and testers
want access to the changes in their integrated form before all of those
changes land in the mainline kernel.  One could pull changes from all of
the interesting subsystem trees, but that would be a big and error-prone
job.”…””}”(hjf	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h MhjU	  hžhubhÆ)”}”(hXf  The answer comes in the form of -next trees, where subsystem trees are
collected for testing and review.  The older of these trees, maintained by
Andrew Morton, is called "-mm" (for memory management, which is how it got
started).  The -mm tree integrates patches from a long list of subsystem
trees; it also has some patches aimed at helping with debugging.”h]”hXj  The answer comes in the form of -next trees, where subsystem trees are
collected for testing and review.  The older of these trees, maintained by
Andrew Morton, is called â€œ-mmâ€ (for memory management, which is how it got
started).  The -mm tree integrates patches from a long list of subsystem
trees; it also has some patches aimed at helping with debugging.”…””}”(hjt	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h MhjU	  hžhubhÆ)”}”(hX§  Beyond that, -mm contains a significant collection of patches which have
been selected by Andrew directly.  These patches may have been posted on a
mailing list, or they may apply to a part of the kernel for which there is
no designated subsystem tree.  As a result, -mm operates as a sort of
subsystem tree of last resort; if there is no other obvious path for a
patch into the mainline, it is likely to end up in -mm.  Miscellaneous
patches which accumulate in -mm will eventually either be forwarded on to
an appropriate subsystem tree or be sent directly to Linus.  In a typical
development cycle, approximately 5-10% of the patches going into the
mainline get there via -mm.”h]”hX§  Beyond that, -mm contains a significant collection of patches which have
been selected by Andrew directly.  These patches may have been posted on a
mailing list, or they may apply to a part of the kernel for which there is
no designated subsystem tree.  As a result, -mm operates as a sort of
subsystem tree of last resort; if there is no other obvious path for a
patch into the mainline, it is likely to end up in -mm.  Miscellaneous
patches which accumulate in -mm will eventually either be forwarded on to
an appropriate subsystem tree or be sent directly to Linus.  In a typical
development cycle, approximately 5-10% of the patches going into the
mainline get there via -mm.”…””}”(hj‚	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h MhjU	  hžhubhÆ)”}”(hŒSThe current -mm patch is available in the "mmotm" (-mm of the moment)
directory at:”h]”hŒWThe current -mm patch is available in the â€œmmotmâ€ (-mm of the moment)
directory at:”…””}”(hj	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h M hjU	  hžhubhõ)”}”(hŒ$https://www.ozlabs.org/~akpm/mmotm/
”h]”hÆ)”}”(hŒ#https://www.ozlabs.org/~akpm/mmotm/”h]”j‰  )”}”(hj¤	  h]”hŒ#https://www.ozlabs.org/~akpm/mmotm/”…””}”(hj¦	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j¤	  uh1jˆ  hj¢	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h M#hjž	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hôhŸh¯h M#hjU	  hžhubhÆ)”}”(hŒUse of the MMOTM tree is likely to be a frustrating experience, though;
there is a definite chance that it will not even compile.”h]”hŒUse of the MMOTM tree is likely to be a frustrating experience, though;
there is a definite chance that it will not even compile.”…””}”(hjÀ	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h M%hjU	  hžhubhÆ)”}”(hXc  The primary tree for next-cycle patch merging is linux-next, maintained by
Stephen Rothwell.  The linux-next tree is, by design, a snapshot of what
the mainline is expected to look like after the next merge window closes.
Linux-next trees are announced on the linux-kernel and linux-next mailing
lists when they are assembled; they can be downloaded from:”h]”hXc  The primary tree for next-cycle patch merging is linux-next, maintained by
Stephen Rothwell.  The linux-next tree is, by design, a snapshot of what
the mainline is expected to look like after the next merge window closes.
Linux-next trees are announced on the linux-kernel and linux-next mailing
lists when they are assembled; they can be downloaded from:”…””}”(hjÎ	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h M(hjU	  hžhubhõ)”}”(hŒ.https://www.kernel.org/pub/linux/kernel/next/
”h]”hÆ)”}”(hŒ-https://www.kernel.org/pub/linux/kernel/next/”h]”j‰  )”}”(hjâ	  h]”hŒ-https://www.kernel.org/pub/linux/kernel/next/”…””}”(hjä	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jâ	  uh1jˆ  hjà	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h M.hjÜ	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hôhŸh¯h M.hjU	  hžhubhÆ)”}”(hŒÔLinux-next has become an integral part of the kernel development process;
all patches merged during a given merge window should really have found
their way into linux-next some time before the merge window opens.”h]”hŒÔLinux-next has become an integral part of the kernel development process;
all patches merged during a given merge window should really have found
their way into linux-next some time before the merge window opens.”…””}”(hjþ	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h M0hjU	  hžhubeh}”(h]”Œ
next-trees”ah ]”h"]”Œ
next trees”ah$]”h&]”uh1h°hh²hžhhŸh¯h Mubh±)”}”(hhh]”(h¶)”}”(hŒStaging trees”h]”hŒStaging trees”…””}”(hj
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhj
  hžhhŸh¯h M6ubhÆ)”}”(hXÈ  The kernel source tree contains the drivers/staging/ directory, where
many sub-directories for drivers or filesystems that are on their way to
being added to the kernel tree live.  They remain in drivers/staging while
they still need more work; once complete, they can be moved into the
kernel proper.  This is a way to keep track of drivers that aren't
up to Linux kernel coding or quality standards, but people may want to use
them and track development.”h]”hXÊ  The kernel source tree contains the drivers/staging/ directory, where
many sub-directories for drivers or filesystems that are on their way to
being added to the kernel tree live.  They remain in drivers/staging while
they still need more work; once complete, they can be moved into the
kernel proper.  This is a way to keep track of drivers that arenâ€™t
up to Linux kernel coding or quality standards, but people may want to use
them and track development.”…””}”(hj%
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h M8hj
  hžhubhÆ)”}”(hX  Greg Kroah-Hartman currently maintains the staging tree.  Drivers that
still need work are sent to him, with each driver having its own
subdirectory in drivers/staging/.  Along with the driver source files, a
TODO file should be present in the directory as well.  The TODO file lists
the pending work that the driver needs for acceptance into the kernel
proper, as well as a list of people that should be Cc'd for any patches to
the driver.  Current rules require that drivers contributed to staging
must, at a minimum, compile properly.”h]”hX  Greg Kroah-Hartman currently maintains the staging tree.  Drivers that
still need work are sent to him, with each driver having its own
subdirectory in drivers/staging/.  Along with the driver source files, a
TODO file should be present in the directory as well.  The TODO file lists
the pending work that the driver needs for acceptance into the kernel
proper, as well as a list of people that should be Ccâ€™d for any patches to
the driver.  Current rules require that drivers contributed to staging
must, at a minimum, compile properly.”…””}”(hj3
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h M@hj
  hžhubhÆ)”}”(hXÑ  Staging can be a relatively easy way to get new drivers into the mainline
where, with luck, they will come to the attention of other developers and
improve quickly.  Entry into staging is not the end of the story, though;
code in staging which is not seeing regular progress will eventually be
removed.  Distributors also tend to be relatively reluctant to enable
staging drivers.  So staging is, at best, a stop on the way toward becoming
a proper mainline driver.”h]”hXÑ  Staging can be a relatively easy way to get new drivers into the mainline
where, with luck, they will come to the attention of other developers and
improve quickly.  Entry into staging is not the end of the story, though;
code in staging which is not seeing regular progress will eventually be
removed.  Distributors also tend to be relatively reluctant to enable
staging drivers.  So staging is, at best, a stop on the way toward becoming
a proper mainline driver.”…””}”(hjA
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h MIhj
  hžhubeh}”(h]”Œstaging-trees”ah ]”h"]”Œstaging trees”ah$]”h&]”uh1h°hh²hžhhŸh¯h M6ubh±)”}”(hhh]”(h¶)”}”(hŒTools”h]”hŒTools”…””}”(hjZ
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhjW
  hžhhŸh¯h MSubhÆ)”}”(hXq  As can be seen from the above text, the kernel development process depends
heavily on the ability to herd collections of patches in various
directions.  The whole thing would not work anywhere near as well as it
does without suitably powerful tools.  Tutorials on how to use these tools
are well beyond the scope of this document, but there is space for a few
pointers.”h]”hXq  As can be seen from the above text, the kernel development process depends
heavily on the ability to herd collections of patches in various
directions.  The whole thing would not work anywhere near as well as it
does without suitably powerful tools.  Tutorials on how to use these tools
are well beyond the scope of this document, but there is space for a few
pointers.”…””}”(hjh
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h MUhjW
  hžhubhÆ)”}”(hXŽ  By far the dominant source code management system used by the kernel
community is git.  Git is one of a number of distributed version control
systems being developed in the free software community.  It is well tuned
for kernel development, in that it performs quite well when dealing with
large repositories and large numbers of patches.  It also has a reputation
for being difficult to learn and use, though it has gotten better over
time.  Some sort of familiarity with git is almost a requirement for kernel
developers; even if they do not use it for their own work, they'll need git
to keep up with what other developers (and the mainline) are doing.”h]”hX  By far the dominant source code management system used by the kernel
community is git.  Git is one of a number of distributed version control
systems being developed in the free software community.  It is well tuned
for kernel development, in that it performs quite well when dealing with
large repositories and large numbers of patches.  It also has a reputation
for being difficult to learn and use, though it has gotten better over
time.  Some sort of familiarity with git is almost a requirement for kernel
developers; even if they do not use it for their own work, theyâ€™ll need git
to keep up with what other developers (and the mainline) are doing.”…””}”(hjv
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h M\hjW
  hžhubhÆ)”}”(hŒPGit is now packaged by almost all Linux distributions.  There is a home
page at:”h]”hŒPGit is now packaged by almost all Linux distributions.  There is a home
page at:”…””}”(hj„
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h MfhjW
  hžhubhõ)”}”(hŒhttps://git-scm.com/
”h]”hÆ)”}”(hŒhttps://git-scm.com/”h]”j‰  )”}”(hj˜
  h]”hŒhttps://git-scm.com/”…””}”(hjš
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j˜
  uh1jˆ  hj–
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Mihj’
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hôhŸh¯h MihjW
  hžhubhÆ)”}”(hŒ6That page has pointers to documentation and tutorials.”h]”hŒ6That page has pointers to documentation and tutorials.”…””}”(hj´
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h MkhjW
  hžhubhÆ)”}”(hŒfAmong the kernel developers who do not use git, the most popular choice is
almost certainly Mercurial:”h]”hŒfAmong the kernel developers who do not use git, the most popular choice is
almost certainly Mercurial:”…””}”(hjÂ
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h MmhjW
  hžhubhõ)”}”(hŒ#https://www.selenic.com/mercurial/
”h]”hÆ)”}”(hŒ"https://www.selenic.com/mercurial/”h]”j‰  )”}”(hjÖ
  h]”hŒ"https://www.selenic.com/mercurial/”…””}”(hjØ
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jÖ
  uh1jˆ  hjÔ
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h MphjÐ
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hôhŸh¯h MphjW
  hžhubhÆ)”}”(hŒdMercurial shares many features with git, but it provides an interface which
many find easier to use.”h]”hŒdMercurial shares many features with git, but it provides an interface which
many find easier to use.”…””}”(hjò
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h MrhjW
  hžhubhÆ)”}”(hŒ,The other tool worth knowing about is Quilt:”h]”hŒ,The other tool worth knowing about is Quilt:”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h MuhjW
  hžhubhõ)”}”(hŒ,https://savannah.nongnu.org/projects/quilt/
”h]”hÆ)”}”(hŒ+https://savannah.nongnu.org/projects/quilt/”h]”j‰  )”}”(hj  h]”hŒ+https://savannah.nongnu.org/projects/quilt/”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j  uh1jˆ  hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Mwhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hôhŸh¯h MwhjW
  hžhubhÆ)”}”(hX”  Quilt is a patch management system, rather than a source code management
system.  It does not track history over time; it is, instead, oriented
toward tracking a specific set of changes against an evolving code base.
Some major subsystem maintainers use quilt to manage patches intended to go
upstream.  For the management of certain kinds of trees (-mm, for example),
quilt is the best tool for the job.”h]”hX”  Quilt is a patch management system, rather than a source code management
system.  It does not track history over time; it is, instead, oriented
toward tracking a specific set of changes against an evolving code base.
Some major subsystem maintainers use quilt to manage patches intended to go
upstream.  For the management of certain kinds of trees (-mm, for example),
quilt is the best tool for the job.”…””}”(hj0  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h MyhjW
  hžhubeh}”(h]”Œtools”ah ]”h"]”Œtools”ah$]”h&]”uh1h°hh²hžhhŸh¯h MSubh±)”}”(hhh]”(h¶)”}”(hŒMailing lists”h]”hŒMailing lists”…””}”(hjI  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhjF  hžhhŸh¯h M‚ubhÆ)”}”(hX  A great deal of Linux kernel development work is done by way of mailing
lists.  It is hard to be a fully-functioning member of the community
without joining at least one list somewhere.  But Linux mailing lists also
represent a potential hazard to developers, who risk getting buried under a
load of electronic mail, running afoul of the conventions used on the Linux
lists, or both.”h]”hX  A great deal of Linux kernel development work is done by way of mailing
lists.  It is hard to be a fully-functioning member of the community
without joining at least one list somewhere.  But Linux mailing lists also
represent a potential hazard to developers, who risk getting buried under a
load of electronic mail, running afoul of the conventions used on the Linux
lists, or both.”…””}”(hjW  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h M„hjF  hžhubhÆ)”}”(hŒTMost kernel mailing lists are hosted at kernel.org; the master list can
be found at:”h]”hŒTMost kernel mailing lists are hosted at kernel.org; the master list can
be found at:”…””}”(hje  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h M‹hjF  hžhubhõ)”}”(hŒhttps://subspace.kernel.org
”h]”hÆ)”}”(hŒhttps://subspace.kernel.org”h]”j‰  )”}”(hjy  h]”hŒhttps://subspace.kernel.org”…””}”(hj{  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jy  uh1jˆ  hjw  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h MŽhjs  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hôhŸh¯h MŽhjF  hžhubhÆ)”}”(hŒwThere are lists hosted elsewhere; please check the MAINTAINERS file for
the list relevant for any particular subsystem.”h]”hŒwThere are lists hosted elsewhere; please check the MAINTAINERS file for
the list relevant for any particular subsystem.”…””}”(hj•  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h MhjF  hžhubhÆ)”}”(hXÖ  The core mailing list for kernel development is, of course, linux-kernel.
This list is an intimidating place to be; volume can reach 500 messages per
day, the amount of noise is high, the conversation can be severely
technical, and participants are not always concerned with showing a high
degree of politeness.  But there is no other place where the kernel
development community comes together as a whole; developers who avoid this
list will miss important information.”h]”hXÖ  The core mailing list for kernel development is, of course, linux-kernel.
This list is an intimidating place to be; volume can reach 500 messages per
day, the amount of noise is high, the conversation can be severely
technical, and participants are not always concerned with showing a high
degree of politeness.  But there is no other place where the kernel
development community comes together as a whole; developers who avoid this
list will miss important information.”…””}”(hj£  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h M“hjF  hžhubhÆ)”}”(hŒ@There are a few hints which can help with linux-kernel survival:”h]”hŒ@There are a few hints which can help with linux-kernel survival:”…””}”(hj±  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h M›hjF  hžhubjú  )”}”(hhh]”(jÿ  )”}”(hŒ“Have the list delivered to a separate folder, rather than your main
mailbox.  One must be able to ignore the stream for sustained periods of
time.
”h]”hÆ)”}”(hŒ’Have the list delivered to a separate folder, rather than your main
mailbox.  One must be able to ignore the stream for sustained periods of
time.”•6?      h]”hŒ’Have the list delivered to a separate folder, rather than your main
mailbox.  One must be able to ignore the stream for sustained periods of
time.”…””}”(hjÆ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h MhjÂ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jþ  hj¿  hžhhŸh¯h Nubjÿ  )”}”(hX  Do not try to follow every conversation - nobody else does.  It is
important to filter on both the topic of interest (though note that
long-running conversations can drift away from the original subject
without changing the email subject line) and the people who are
participating.
”h]”hÆ)”}”(hX  Do not try to follow every conversation - nobody else does.  It is
important to filter on both the topic of interest (though note that
long-running conversations can drift away from the original subject
without changing the email subject line) and the people who are
participating.”h]”hX  Do not try to follow every conversation - nobody else does.  It is
important to filter on both the topic of interest (though note that
long-running conversations can drift away from the original subject
without changing the email subject line) and the people who are
participating.”…””}”(hjÞ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h M¡hjÚ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jþ  hj¿  hžhhŸh¯h Nubjÿ  )”}”(hŒZDo not feed the trolls.  If somebody is trying to stir up an angry
response, ignore them.
”h]”hÆ)”}”(hŒYDo not feed the trolls.  If somebody is trying to stir up an angry
response, ignore them.”h]”hŒYDo not feed the trolls.  If somebody is trying to stir up an angry
response, ignore them.”…””}”(hjö  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h M§hjò  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jþ  hj¿  hžhhŸh¯h Nubjÿ  )”}”(hX‚  When responding to linux-kernel email (or that on other lists) preserve
the Cc: header for all involved.  In the absence of a strong reason (such
as an explicit request), you should never remove recipients.  Always make
sure that the person you are responding to is in the Cc: list.  This
convention also makes it unnecessary to explicitly ask to be copied on
replies to your postings.
”h]”hÆ)”}”(hX  When responding to linux-kernel email (or that on other lists) preserve
the Cc: header for all involved.  In the absence of a strong reason (such
as an explicit request), you should never remove recipients.  Always make
sure that the person you are responding to is in the Cc: list.  This
convention also makes it unnecessary to explicitly ask to be copied on
replies to your postings.”h]”hX  When responding to linux-kernel email (or that on other lists) preserve
the Cc: header for all involved.  In the absence of a strong reason (such
as an explicit request), you should never remove recipients.  Always make
sure that the person you are responding to is in the Cc: list.  This
convention also makes it unnecessary to explicitly ask to be copied on
replies to your postings.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Mªhj
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jþ  hj¿  hžhhŸh¯h Nubjÿ  )”}”(hŒ¤Search the list archives (and the net as a whole) before asking
questions.  Some developers can get impatient with people who clearly
have not done their homework.
”h]”hÆ)”}”(hŒ£Search the list archives (and the net as a whole) before asking
questions.  Some developers can get impatient with people who clearly
have not done their homework.”h]”hŒ£Search the list archives (and the net as a whole) before asking
questions.  Some developers can get impatient with people who clearly
have not done their homework.”…””}”(hj&  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h M±hj"  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jþ  hj¿  hžhhŸh¯h Nubjÿ  )”}”(hX  Use interleaved ("inline") replies, which makes your response easier to
read. (i.e. avoid top-posting -- the practice of putting your answer above
the quoted text you are responding to.) For more details, see
:ref:`Documentation/process/submitting-patches.rst <interleaved_replies>`.
”h]”hÆ)”}”(hX  Use interleaved ("inline") replies, which makes your response easier to
read. (i.e. avoid top-posting -- the practice of putting your answer above
the quoted text you are responding to.) For more details, see
:ref:`Documentation/process/submitting-patches.rst <interleaved_replies>`.”h]”(hŒÕUse interleaved (â€œinlineâ€) replies, which makes your response easier to
read. (i.e. avoid top-posting -- the practice of putting your answer above
the quoted text you are responding to.) For more details, see
”…””}”(hj>  hžhhŸNh Nubh)”}”(hŒI:ref:`Documentation/process/submitting-patches.rst <interleaved_replies>`”h]”hŒinline”“”)”}”(hjH  h]”hŒ,Documentation/process/submitting-patches.rst”…””}”(hjL  hžhhŸNh Nubah}”(h]”h ]”(Œxref”Œstd”Œstd-ref”eh"]”h$]”h&]”uh1jJ  hjF  ubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”Œprocess/2.Process”Œ	refdomain”jW  Œreftype”Œref”Œrefexplicit”ˆŒrefwarn”ˆŒ	reftarget”Œinterleaved_replies”uh1hhŸh¯h Mµhj>  ubhŒ.”…””}”(hj>  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Mµhj:  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jþ  hj¿  hžhhŸh¯h Nubjÿ  )”}”(hŒ–Ask on the correct mailing list.  Linux-kernel may be the general meeting
point, but it is not the best place to find developers from all
subsystems.
”h]”hÆ)”}”(hŒ•Ask on the correct mailing list.  Linux-kernel may be the general meeting
point, but it is not the best place to find developers from all
subsystems.”h]”hŒ•Ask on the correct mailing list.  Linux-kernel may be the general meeting
point, but it is not the best place to find developers from all
subsystems.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Mºhj{  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jþ  hj¿  hžhhŸh¯h Nubeh}”(h]”h ]”h"]”h$]”h&]”jN  jO  uh1jù  hŸh¯h MhjF  hžhubhÆ)”}”(hXõ  The last point - finding the correct mailing list - is a common place for
beginning developers to go wrong.  Somebody who asks a networking-related
question on linux-kernel will almost certainly receive a polite suggestion
to ask on the netdev list instead, as that is the list frequented by most
networking developers.  Other lists exist for the SCSI, video4linux, IDE,
filesystem, etc. subsystems.  The best place to look for mailing lists is
in the MAINTAINERS file packaged with the kernel source.”h]”hXõ  The last point - finding the correct mailing list - is a common place for
beginning developers to go wrong.  Somebody who asks a networking-related
question on linux-kernel will almost certainly receive a polite suggestion
to ask on the netdev list instead, as that is the list frequented by most
networking developers.  Other lists exist for the SCSI, video4linux, IDE,
filesystem, etc. subsystems.  The best place to look for mailing lists is
in the MAINTAINERS file packaged with the kernel source.”…””}”(hj™  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h M¾hjF  hžhubeh}”(h]”Œmailing-lists”ah ]”h"]”Œmailing lists”ah$]”h&]”uh1h°hh²hžhhŸh¯h M‚ubh±)”}”(hhh]”(h¶)”}”(hŒ'Getting started with Kernel development”h]”hŒ'Getting started with Kernel development”…””}”(hj²  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhj¯  hžhhŸh¯h MÈubhÆ)”}”(hŒÜQuestions about how to get started with the kernel development process are
common - from both individuals and companies.  Equally common are missteps
which make the beginning of the relationship harder than it has to be.”h]”hŒÜQuestions about how to get started with the kernel development process are
common - from both individuals and companies.  Equally common are missteps
which make the beginning of the relationship harder than it has to be.”…””}”(hjÀ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h MÊhj¯  hžhubhÆ)”}”(hXL  Companies often look to hire well-known developers to get a development
group started.  This can, in fact, be an effective technique.  But it also
tends to be expensive and does not do much to grow the pool of experienced
kernel developers.  It is possible to bring in-house developers up to speed
on Linux kernel development, given the investment of a bit of time.  Taking
this time can endow an employer with a group of developers who understand
the kernel and the company both, and who can help to train others as well.
Over the medium term, this is often the more profitable approach.”h]”hXL  Companies often look to hire well-known developers to get a development
group started.  This can, in fact, be an effective technique.  But it also
tends to be expensive and does not do much to grow the pool of experienced
kernel developers.  It is possible to bring in-house developers up to speed
on Linux kernel development, given the investment of a bit of time.  Taking
this time can endow an employer with a group of developers who understand
the kernel and the company both, and who can help to train others as well.
Over the medium term, this is often the more profitable approach.”…””}”(hjÎ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h MÎhj¯  hžhubhÆ)”}”(hXi  Individual developers are often, understandably, at a loss for a place to
start.  Beginning with a large project can be intimidating; one often wants
to test the waters with something smaller first.  This is the point where
some developers jump into the creation of patches fixing spelling errors or
minor coding style issues.  Unfortunately, such patches create a level of
noise which is distracting for the development community as a whole, so,
increasingly, they are looked down upon.  New developers wishing to
introduce themselves to the community will not get the sort of reception
they wish for by these means.”h]”hXi  Individual developers are often, understandably, at a loss for a place to
start.  Beginning with a large project can be intimidating; one often wants
to test the waters with something smaller first.  This is the point where
some developers jump into the creation of patches fixing spelling errors or
minor coding style issues.  Unfortunately, such patches create a level of
noise which is distracting for the development community as a whole, so,
increasingly, they are looked down upon.  New developers wishing to
introduce themselves to the community will not get the sort of reception
they wish for by these means.”…””}”(hjÜ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h M×hj¯  hžhubhÆ)”}”(hŒ>Andrew Morton gives this advice for aspiring kernel developers”h]”hŒ>Andrew Morton gives this advice for aspiring kernel developers”…””}”(hjê  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Máhj¯  hžhubhŒliteral_block”“”)”}”(hXD  The #1 project for all kernel beginners should surely be "make sure
that the kernel runs perfectly at all times on all machines which
you can lay your hands on".  Usually the way to do this is to work
with others on getting things fixed up (this can require
persistence!) but that's fine - it's a part of kernel development.”h]”hXD  The #1 project for all kernel beginners should surely be "make sure
that the kernel runs perfectly at all times on all machines which
you can lay your hands on".  Usually the way to do this is to work
with others on getting things fixed up (this can require
persistence!) but that's fine - it's a part of kernel development.”…””}”hjú  sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1jø  hŸh¯h Måhj¯  hžhubhÆ)”}”(hŒ#(https://lwn.net/Articles/283982/).”h]”(hŒ(”…””}”(hj
  hžhhŸNh Nubj‰  )”}”(hŒ https://lwn.net/Articles/283982/”h]”hŒ https://lwn.net/Articles/283982/”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j  uh1jˆ  hj
  ubhŒ).”…””}”(hj
  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Mëhj¯  hžhubhÆ)”}”(hXd  In the absence of obvious problems to fix, developers are advised to look
at the current lists of regressions and open bugs in general.  There is
never any shortage of issues in need of fixing; by addressing these issues,
developers will gain experience with the process while, at the same time,
building respect with the rest of the development community.”h]”hXd  In the absence of obvious problems to fix, developers are advised to look
at the current lists of regressions and open bugs in general.  There is
never any shortage of issues in need of fixing; by addressing these issues,
developers will gain experience with the process while, at the same time,
building respect with the rest of the development community.”…””}”(hj+  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Míhj¯  hžhubeh}”(h]”Œ'getting-started-with-kernel-development”ah ]”h"]”Œ'getting started with kernel development”ah$]”h&]”uh1h°hh²hžhhŸh¯h MÈubeh}”(h]”(Œ!how-the-development-process-works”h®eh ]”h"]”(Œ!how the development process works”Œdevelopment_process”eh$]”h&]”uh1h°hhhžhhŸh¯h KŒexpect_referenced_by_name”}”jG  h£sŒexpect_referenced_by_id”}”h®h£subeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¯uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(hµNŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”j$  Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jp  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¯Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”h®]”h£asŒnameids”}”(jG  h®jF  jC  j·  j´  jå  jâ  jR	  jO	  j
  j
  jT
  jQ
  jC  j@  j¬  j©  j>  j;  uŒ	nametypes”}”(jG  ˆjF  ‰j·  ‰jå  ‰jR	  ‰j
  ‰jT
  ‰jC  ‰j¬  ‰j>  ‰uh}”(h®h²jC  h²j´  hÕjâ  jº  jO	  jè  j
  jU	  jQ
  j
  j@  jW
  j©  jF  j;  j¯  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”(hŒsystem_message”“”)”}”(hhh]”hÆ)”}”(hŒeUnexpected possible title overline or transition.
Treating it as ordinary text because it's so short.”h]”hŒgUnexpected possible title overline or transition.
Treating it as ordinary text because itâ€™s so short.”…””}”(hjØ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhjÕ  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”ŒINFO”Œline”K{Œsource”h¯uh1jÓ  hjà  ubjÔ  )”}”(hhh]”hÆ)”}”(hŒeUnexpected possible title overline or transition.
Treating it as ordinary text because it's so short.”h]”hŒgUnexpected possible title overline or transition.
Treating it as ordinary text because itâ€™s so short.”…””}”(hjô  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhjñ  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”jî  Œline”K{Œsource”h¯uh1jÓ  hj÷  ubeŒtransform_messages”]”jÔ  )”}”(hhh]”hÆ)”}”(hhh]”hŒ9Hyperlink target "development-process" is not referenced.”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhj  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”jî  Œsource”h¯Œline”Kuh1jÓ  ubaŒtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.