sphinx.addnodesdocument)}( rawsourcechildren]( translations LanguagesNode)}(hhh](h pending_xref)}(hhh]docutils.nodesTextChinese (Simplified)}parenthsba attributes}(ids]classes]names]dupnames]backrefs] refdomainstdreftypedoc reftarget//translations/zh_CN/process/stable-kernel-rulesmodnameN classnameN refexplicitutagnamehhh ubh)}(hhh]hChinese (Traditional)}hh2sbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget//translations/zh_TW/process/stable-kernel-rulesmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hItalian}hhFsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget//translations/it_IT/process/stable-kernel-rulesmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hJapanese}hhZsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget//translations/ja_JP/process/stable-kernel-rulesmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hKorean}hhnsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget//translations/ko_KR/process/stable-kernel-rulesmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hPortuguese (Brazilian)}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget//translations/pt_BR/process/stable-kernel-rulesmodnameN classnameN refexplicituh1hhh ubh)}(hhh]hSpanish}hhsbah}(h]h ]h"]h$]h&] refdomainh)reftypeh+ reftarget//translations/sp_SP/process/stable-kernel-rulesmodnameN classnameN refexplicituh1hhh ubeh}(h]h ]h"]h$]h&]current_languageEnglishuh1h hh _documenthsourceNlineNubhtarget)}(h.. _stable_kernel_rules:h]h}(h]h ]h"]h$]h&]refidstable-kernel-rulesuh1hhKhhhhhI/var/lib/git/docbuild/linux/Documentation/process/stable-kernel-rules.rstubhsection)}(hhh](htitle)}(h?Everything you ever wanted to know about Linux -stable releasesh]h?Everything you ever wanted to know about Linux -stable releases}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhhhhhKubh paragraph)}(h\Rules on what kind of patches are accepted, and which ones are not, into the "-stable" tree:h]h`Rules on what kind of patches are accepted, and which ones are not, into the “-stable” tree:}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhhhhubh bullet_list)}(hhh](h list_item)}(hHIt or an equivalent fix must already exist in Linux mainline (upstream).h]h)}(hhh]hHIt or an equivalent fix must already exist in Linux mainline (upstream).}(hhhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hhubah}(h]h ]h"]h$]h&]uh1hhhhhhhhNubh)}(h(It must be obviously correct and tested.h]h)}(hj h]h(It must be obviously correct and tested.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hjubah}(h]h ]h"]h$]h&]uh1hhhhhhhhNubh)}(h1It cannot be bigger than 100 lines, with context.h]h)}(hj h]h1It cannot be bigger than 100 lines, with context.}(hj"hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK hjubah}(h]h ]h"]h$]h&]uh1hhhhhhhhNubh)}(haIt must follow the :ref:`Documentation/process/submitting-patches.rst ` rules.h]h)}(haIt must follow the :ref:`Documentation/process/submitting-patches.rst ` rules.h](hIt must follow the }(hj9hhhNhNubh)}(hG:ref:`Documentation/process/submitting-patches.rst `h]hinline)}(hjCh]h,Documentation/process/submitting-patches.rst}(hjGhhhNhNubah}(h]h ](xrefstdstd-refeh"]h$]h&]uh1jEhjAubah}(h]h ]h"]h$]h&]refdocprocess/stable-kernel-rules refdomainjRreftyperef refexplicitrefwarn reftargetsubmittingpatchesuh1hhhhK hj9ubh rules.}(hj9hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK hj5ubah}(h]h ]h"]h$]h&]uh1hhhhhhhhNubh)}(hXIt must either fix a real bug that bothers people or just add a device ID. To elaborate on the former: - It fixes a problem like an oops, a hang, data corruption, a real security issue, a hardware quirk, a build error (but not for things marked CONFIG_BROKEN), or some "oh, that's not good" issue. - Serious issues as reported by a user of a distribution kernel may also be considered if they fix a notable performance or interactivity issue. As these fixes are not as obvious and have a higher risk of a subtle regression they should only be submitted by a distribution kernel maintainer and include an addendum linking to a bugzilla entry if it exists and additional information on the user-visible impact. - No "This could be a problem..." type of things like a "theoretical race condition", unless an explanation of how the bug can be exploited is also provided. - No "trivial" fixes without benefit for users (spelling changes, whitespace cleanups, etc). h](h)}(hfIt must either fix a real bug that bothers people or just add a device ID. To elaborate on the former:h]hfIt must either fix a real bug that bothers people or just add a device ID. To elaborate on the former:}(hjzhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjvubh)}(hhh](h)}(hIt fixes a problem like an oops, a hang, data corruption, a real security issue, a hardware quirk, a build error (but not for things marked CONFIG_BROKEN), or some "oh, that's not good" issue.h]h)}(hIt fixes a problem like an oops, a hang, data corruption, a real security issue, a hardware quirk, a build error (but not for things marked CONFIG_BROKEN), or some "oh, that's not good" issue.h]hIt fixes a problem like an oops, a hang, data corruption, a real security issue, a hardware quirk, a build error (but not for things marked CONFIG_BROKEN), or some “oh, that’s not good” issue.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1hhjubh)}(hXSerious issues as reported by a user of a distribution kernel may also be considered if they fix a notable performance or interactivity issue. As these fixes are not as obvious and have a higher risk of a subtle regression they should only be submitted by a distribution kernel maintainer and include an addendum linking to a bugzilla entry if it exists and additional information on the user-visible impact.h]h)}(hXSerious issues as reported by a user of a distribution kernel may also be considered if they fix a notable performance or interactivity issue. As these fixes are not as obvious and have a higher risk of a subtle regression they should only be submitted by a distribution kernel maintainer and include an addendum linking to a bugzilla entry if it exists and additional information on the user-visible impact.h]hXSerious issues as reported by a user of a distribution kernel may also be considered if they fix a notable performance or interactivity issue. As these fixes are not as obvious and have a higher risk of a subtle regression they should only be submitted by a distribution kernel maintainer and include an addendum linking to a bugzilla entry if it exists and additional information on the user-visible impact.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1hhjubh)}(hNo "This could be a problem..." type of things like a "theoretical race condition", unless an explanation of how the bug can be exploited is also provided.h]h)}(hNo "This could be a problem..." type of things like a "theoretical race condition", unless an explanation of how the bug can be exploited is also provided.h]hNo “This could be a problem...” type of things like a “theoretical race condition”, unless an explanation of how the bug can be exploited is also provided.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1hhjubh)}(h\No "trivial" fixes without benefit for users (spelling changes, whitespace cleanups, etc). h]h)}(hZNo "trivial" fixes without benefit for users (spelling changes, whitespace cleanups, etc).h]h^No “trivial” fixes without benefit for users (spelling changes, whitespace cleanups, etc).}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1hhjubeh}(h]h ]h"]h$]h&]bullet-uh1hhhhKhjvubeh}(h]h ]h"]h$]h&]uh1hhhhhhNhNubeh}(h]h ]h"]h$]h&]jjuh1hhhhK hhhhubh)}(hhh](h)}(h4Procedure for submitting patches to the -stable treeh]h4Procedure for submitting patches to the -stable tree}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhK#ubhnote)}(hSecurity patches should not be handled (solely) by the -stable review process but should follow the procedures in :ref:`Documentation/process/security-bugs.rst `.h]h)}(hSecurity patches should not be handled (solely) by the -stable review process but should follow the procedures in :ref:`Documentation/process/security-bugs.rst `.h](hrSecurity patches should not be handled (solely) by the -stable review process but should follow the procedures in }(hjhhhNhNubh)}(h=:ref:`Documentation/process/security-bugs.rst `h]jF)}(hj h]h'Documentation/process/security-bugs.rst}(hj"hhhNhNubah}(h]h ](jQstdstd-refeh"]h$]h&]uh1jEhjubah}(h]h ]h"]h$]h&]refdocj^ refdomainj,reftyperef refexplicitrefwarnjd securitybugsuh1hhhhK'hjubh.}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhK'hjubah}(h]h ]h"]h$]h&]uh1jhjhhhhhNubh)}(h # 3.3.x: a1f84a3: sched: Check for idle Cc: # 3.3.x: 1b9508f: sched: Rate-limit newidle Cc: # 3.3.x: fd21073: sched: Fix affinity logic Cc: # 3.3.x Signed-off-by: Ingo Molnar The tag sequence has the meaning of:: git cherry-pick a1f84a3 git cherry-pick 1b9508f git cherry-pick fd21073 git cherry-pick Note that for a patch series, you do not have to list as prerequisites the patches present in the series itself. For example, if you have the following patch series:: patch1 patch2 where patch2 depends on patch1, you do not have to list patch1 as prerequisite of patch2 if you have already marked patch1 for stable inclusion. h](h)}(h?Specify any additional patch prerequisites for cherry picking::h]h>Specify any additional patch prerequisites for cherry picking:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKUhjubj)}(hX&Cc: # 3.3.x: a1f84a3: sched: Check for idle Cc: # 3.3.x: 1b9508f: sched: Rate-limit newidle Cc: # 3.3.x: fd21073: sched: Fix affinity logic Cc: # 3.3.x Signed-off-by: Ingo Molnar h]hX&Cc: # 3.3.x: a1f84a3: sched: Check for idle Cc: # 3.3.x: 1b9508f: sched: Rate-limit newidle Cc: # 3.3.x: fd21073: sched: Fix affinity logic Cc: # 3.3.x Signed-off-by: Ingo Molnar }hjsbah}(h]h ]h"]h$]h&]jjuh1jhhhKWhjubh)}(h%The tag sequence has the meaning of::h]h$The tag sequence has the meaning of:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK]hjubj)}(hegit cherry-pick a1f84a3 git cherry-pick 1b9508f git cherry-pick fd21073 git cherry-pick h]hegit cherry-pick a1f84a3 git cherry-pick 1b9508f git cherry-pick fd21073 git cherry-pick }hjsbah}(h]h ]h"]h$]h&]jjuh1jhhhK_hjubh)}(hNote that for a patch series, you do not have to list as prerequisites the patches present in the series itself. For example, if you have the following patch series::h]hNote that for a patch series, you do not have to list as prerequisites the patches present in the series itself. For example, if you have the following patch series:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKdhjubj)}(h patch1 patch2h]h patch1 patch2}hj sbah}(h]h ]h"]h$]h&]jjuh1jhhhKhhjubh)}(hwhere patch2 depends on patch1, you do not have to list patch1 as prerequisite of patch2 if you have already marked patch1 for stable inclusion.h]hwhere patch2 depends on patch1, you do not have to list patch1 as prerequisite of patch2 if you have already marked patch1 for stable inclusion.}(hj.hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKkhjubeh}(h]h ]h"]h$]h&]uh1hhjhhhhhNubh)}(hX:Point out kernel version prerequisites:: Cc: # 3.3.x The tag has the meaning of:: git cherry-pick For each "-stable" tree starting with the specified version. Note, such tagging is unnecessary if the stable team can derive the appropriate versions from Fixes: tags. h](h)}(h(Point out kernel version prerequisites::h]h'Point out kernel version prerequisites:}(hjFhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKohjBubj)}(h$Cc: # 3.3.xh]h$Cc: # 3.3.x}hjTsbah}(h]h ]h"]h$]h&]jjuh1jhhhKqhjBubh)}(hThe tag has the meaning of::h]hThe tag has the meaning of:}(hjbhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKshjBubj)}(hgit cherry-pick h]hgit cherry-pick }hjpsbah}(h]h ]h"]h$]h&]jjuh1jhhhKuhjBubh)}(h # after -rc3 h](h)}(hDelay pick up of patches::h]hDelay pick up of patches:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhK|hjubj)}(h)Cc: # after -rc3h]h)Cc: # after -rc3}hjsbah}(h]h ]h"]h$]h&]jjuh1jhhhK~hjubeh}(h]h ]h"]h$]h&]uh1hhjhhhhhNubh)}(hqPoint out known problems:: Cc: # see patch description, needs adjustments for <= 6.3 h](h)}(hPoint out known problems::h]hPoint out known problems:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubj)}(hRCc: # see patch description, needs adjustments for <= 6.3h]hRCc: # see patch description, needs adjustments for <= 6.3}hjsbah}(h]h ]h"]h$]h&]jjuh1jhhhKhjubeh}(h]h ]h"]h$]h&]uh1hhjhhhhhNubeh}(h]h ]h"]h$]h&]j*uh1hhhhKUhjdhhubh)}(hThere furthermore is a variant of the stable tag you can use to make the stable team's backporting tools (e.g AUTOSEL or scripts that look for commits containing a 'Fixes:' tag) ignore a change::h]hThere furthermore is a variant of the stable tag you can use to make the stable team’s backporting tools (e.g AUTOSEL or scripts that look for commits containing a ‘Fixes:’ tag) ignore a change:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjdhhubj)}(hICc: # reason goes here, and must be presenth]hICc: # reason goes here, and must be present}hjsbah}(h]h ]h"]h$]h&]jjuh1jhhhKhjdhhubh)}(h .. _option_2:h]h}(h]h ]h"]h$]h&]hoption-2uh1hhKhjdhhhhubeh}(h](jcid1eh ]h"](option 1option_1eh$]h&]uh1hhjhhhhhKDexpect_referenced_by_name}j jYsexpect_referenced_by_id}jcjYsubh)}(hhh](h)}(hOption 2h]hOption 2}(hj*hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj'hhhhhKubh)}(hIf the patch already has been merged to mainline, send an email to stable@vger.kernel.org containing the subject of the patch, the commit ID, why you think it should be applied, and what kernel versions you wish it to be applied to.h](hCIf the patch already has been merged to mainline, send an email to }(hj8hhhNhNubh reference)}(hstable@vger.kernel.orgh]hstable@vger.kernel.org}(hjBhhhNhNubah}(h]h ]h"]h$]h&]refurimailto:stable@vger.kernel.orguh1j@hj8ubh containing the subject of the patch, the commit ID, why you think it should be applied, and what kernel versions you wish it to be applied to.}(hj8hhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhj'hhubh)}(h .. _option_3:h]h}(h]h ]h"]h$]h&]hoption-3uh1hhKhj'hhhhubeh}(h](jid2eh ]h"](option 2option_2eh$]h&]uh1hhjhhhhhKj#}jmjsj%}jjsubh)}(hhh](h)}(hOption 3h]hOption 3}(hjuhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjrhhhhhKubh)}(hX(Send the patch, after verifying that it follows the above rules, to stable@vger.kernel.org and mention the kernel versions you wish it to be applied to. When doing so, you must note the upstream commit ID in the changelog of your submission with a separate line above the commit text, like this::h](hDSend the patch, after verifying that it follows the above rules, to }(hjhhhNhNubjA)}(hstable@vger.kernel.orgh]hstable@vger.kernel.org}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurimailto:stable@vger.kernel.orguh1j@hjubh and mention the kernel versions you wish it to be applied to. When doing so, you must note the upstream commit ID in the changelog of your submission with a separate line above the commit text, like this:}(hjhhhNhNubeh}(h]h ]h"]h$]h&]uh1hhhhKhjrhhubj)}(hcommit upstream.h]hcommit upstream.}hjsbah}(h]h ]h"]h$]h&]jjuh1jhhhKhjrhhubh)}(hOr alternatively::h]hOr alternatively:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjrhhubj)}(h[ Upstream commit ]h]h[ Upstream commit ]}hjsbah}(h]h ]h"]h$]h&]jjuh1jhhhKhjrhhubh)}(hIf the submitted patch deviates from the original upstream patch (for example because it had to be adjusted for the older API), this must be very clearly documented and justified in the patch description.h]hIf the submitted patch deviates from the original upstream patch (for example because it had to be adjusted for the older API), this must be very clearly documented and justified in the patch description.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjrhhubeh}(h](jfid3eh ]h"](option 3option_3eh$]h&]uh1hhjhhhhhKj#}jj\sj%}jfj\subeh}(h]3procedure-for-submitting-patches-to-the-stable-treeah ]h"]4procedure for submitting patches to the -stable treeah$]h&]uh1hhhhhhhhK#ubh)}(hhh](h)}(hFollowing the submissionh]hFollowing the submission}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKubh)}(hThe sender will receive an ACK when the patch has been accepted into the queue, or a NAK if the patch is rejected. This response might take a few days, according to the schedules of the stable team members.h]hThe sender will receive an ACK when the patch has been accepted into the queue, or a NAK if the patch is rejected. This response might take a few days, according to the schedules of the stable team members.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubh)}(hIf accepted, the patch will be added to the -stable queue, for review by other developers and by the relevant subsystem maintainer.h]hIf accepted, the patch will be added to the -stable queue, for review by other developers and by the relevant subsystem maintainer.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhhubeh}(h]following-the-submissionah ]h"]following the submissionah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(h Review cycleh]h Review cycle}(hj(hhhNhNubah}(h]h ]h"]h$]h&]uh1hhj%hhhhhKubh)}(hhh](h)}(hWhen the -stable maintainers decide for a review cycle, the patches will be sent to the review committee, and the maintainer of the affected area of the patch (unless the submitter is the maintainer of the area) and CC: to the linux-kernel mailing list.h]h)}(hWhen the -stable maintainers decide for a review cycle, the patches will be sent to the review committee, and the maintainer of the affected area of the patch (unless the submitter is the maintainer of the area) and CC: to the linux-kernel mailing list.h]hWhen the -stable maintainers decide for a review cycle, the patches will be sent to the review committee, and the maintainer of the affected area of the patch (unless the submitter is the maintainer of the area) and CC: to the linux-kernel mailing list.}(hj=hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhj9ubah}(h]h ]h"]h$]h&]uh1hhj6hhhhhNubh)}(hCThe review committee has 48 hours in which to ACK or NAK the patch.h]h)}(hjSh]hCThe review committee has 48 hours in which to ACK or NAK the patch.}(hjUhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjQubah}(h]h ]h"]h$]h&]uh1hhj6hhhhhNubh)}(hIf the patch is rejected by a member of the committee, or linux-kernel members object to the patch, bringing up issues that the maintainers and members did not realize, the patch will be dropped from the queue.h]h)}(hIf the patch is rejected by a member of the committee, or linux-kernel members object to the patch, bringing up issues that the maintainers and members did not realize, the patch will be dropped from the queue.h]hIf the patch is rejected by a member of the committee, or linux-kernel members object to the patch, bringing up issues that the maintainers and members did not realize, the patch will be dropped from the queue.}(hjlhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjhubah}(h]h ]h"]h$]h&]uh1hhj6hhhhhNubh)}(hqThe ACKed patches will be posted again as part of release candidate (-rc) to be tested by developers and testers.h]h)}(hqThe ACKed patches will be posted again as part of release candidate (-rc) to be tested by developers and testers.h]hqThe ACKed patches will be posted again as part of release candidate (-rc) to be tested by developers and testers.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1hhj6hhhhhNubh)}(hUsually only one -rc release is made, however if there are any outstanding issues, some patches may be modified or dropped or additional patches may be queued. Additional -rc releases are then released and tested until no issues are found.h]h)}(hUsually only one -rc release is made, however if there are any outstanding issues, some patches may be modified or dropped or additional patches may be queued. Additional -rc releases are then released and tested until no issues are found.h]hUsually only one -rc release is made, however if there are any outstanding issues, some patches may be modified or dropped or additional patches may be queued. Additional -rc releases are then released and tested until no issues are found.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1hhj6hhhhhNubh)}(hResponding to the -rc releases can be done on the mailing list by sending a "Tested-by:" email with any testing information desired. The "Tested-by:" tags will be collected and added to the release commit.h]h)}(hResponding to the -rc releases can be done on the mailing list by sending a "Tested-by:" email with any testing information desired. The "Tested-by:" tags will be collected and added to the release commit.h]hResponding to the -rc releases can be done on the mailing list by sending a “Tested-by:” email with any testing information desired. The “Tested-by:” tags will be collected and added to the release commit.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1hhj6hhhhhNubh)}(hvAt the end of the review cycle, the new -stable release will be released containing all the queued and tested patches.h]h)}(hvAt the end of the review cycle, the new -stable release will be released containing all the queued and tested patches.h]hvAt the end of the review cycle, the new -stable release will be released containing all the queued and tested patches.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1hhj6hhhhhNubh)}(hSecurity patches will be accepted into the -stable tree directly from the security kernel team, and not go through the normal review cycle. Contact the kernel security team for more details on this procedure. h]h)}(hSecurity patches will be accepted into the -stable tree directly from the security kernel team, and not go through the normal review cycle. Contact the kernel security team for more details on this procedure.h]hSecurity patches will be accepted into the -stable tree directly from the security kernel team, and not go through the normal review cycle. Contact the kernel security team for more details on this procedure.}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1hhj6hhhhhNubeh}(h]h ]h"]h$]h&]jjuh1hhhhKhj%hhubeh}(h] review-cycleah ]h"] review cycleah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(hTreesh]hTrees}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKubh)}(hhh](h)}(hThe queues of patches, for both completed versions and in progress versions can be found at: https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git h](h)}(h\The queues of patches, for both completed versions and in progress versions can be found at:h]h\The queues of patches, for both completed versions and in progress versions can be found at:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubh block_quote)}(hHhttps://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git h]h)}(hGhttps://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.gith]jA)}(hj4h]hGhttps://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git}(hj6hhhNhNubah}(h]h ]h"]h$]h&]refurij4uh1j@hj2ubah}(h]h ]h"]h$]h&]uh1hhhhKhj.ubah}(h]h ]h"]h$]h&]uh1j,hhhKhjubeh}(h]h ]h"]h$]h&]uh1hhjhhhhhNubh)}(hThe finalized and tagged releases of all stable kernels can be found in separate branches per version at: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git h](h)}(hiThe finalized and tagged releases of all stable kernels can be found in separate branches per version at:h]hiThe finalized and tagged releases of all stable kernels can be found in separate branches per version at:}(hjZhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjVubj-)}(hAhttps://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git h]h)}(h@https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.gith]jA)}(hjnh]h@https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git}(hjphhhNhNubah}(h]h ]h"]h$]h&]refurijnuh1j@hjlubah}(h]h ]h"]h$]h&]uh1hhhhKhjhubah}(h]h ]h"]h$]h&]uh1j,hhhKhjVubeh}(h]h ]h"]h$]h&]uh1hhjhhhhhNubh)}(hXyThe release candidate of all stable kernel versions can be found at: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/ .. warning:: The -stable-rc tree is a snapshot in time of the stable-queue tree and will change frequently, hence will be rebased often. It should only be used for testing purposes (e.g. to be consumed by CI systems). h](h)}(hDThe release candidate of all stable kernel versions can be found at:h]hDThe release candidate of all stable kernel versions can be found at:}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubj-)}(hLhttps://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/ h]h)}(hKhttps://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/h]jA)}(hjh]hKhttps://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/}(hjhhhNhNubah}(h]h ]h"]h$]h&]refurijuh1j@hjubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1j,hhhKhjubhwarning)}(hThe -stable-rc tree is a snapshot in time of the stable-queue tree and will change frequently, hence will be rebased often. It should only be used for testing purposes (e.g. to be consumed by CI systems).h]h)}(hThe -stable-rc tree is a snapshot in time of the stable-queue tree and will change frequently, hence will be rebased often. It should only be used for testing purposes (e.g. to be consumed by CI systems).h]hThe -stable-rc tree is a snapshot in time of the stable-queue tree and will change frequently, hence will be rebased often. It should only be used for testing purposes (e.g. to be consumed by CI systems).}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1jhjubeh}(h]h ]h"]h$]h&]uh1hhjhhhNhNubeh}(h]h ]h"]h$]h&]jjuh1hhhhKhjhhubeh}(h]treesah ]h"]treesah$]h&]uh1hhhhhhhhKubh)}(hhh](h)}(hReview committeeh]hReview committee}(hjhhhNhNubah}(h]h ]h"]h$]h&]uh1hhjhhhhhKubh)}(hhh]h)}(hlThis is made up of a number of kernel developers who have volunteered for this task, and a few that haven't.h]h)}(hlThis is made up of a number of kernel developers who have volunteered for this task, and a few that haven't.h]hnThis is made up of a number of kernel developers who have volunteered for this task, and a few that haven’t.}(hj hhhNhNubah}(h]h ]h"]h$]h&]uh1hhhhKhjubah}(h]h ]h"]h$]h&]uh1hhjhhhhhNubah}(h]h ]h"]h$]h&]jjuh1hhhhKhjhhubeh}(h]review-committeeah ]h"]review committeeah$]h&]uh1hhhhhhhhKubeh}(h](>everything-you-ever-wanted-to-know-about-linux-stable-releasesheh ]h"](?everything you ever wanted to know about linux -stable releasesstable_kernel_ruleseh$]h&]uh1hhhhhhhhKj#}j2hsj%}hhsubeh}(h]h ]h"]h$]h&]sourcehuh1hcurrent_sourceN current_lineNsettingsdocutils.frontendValues)}(hN generatorN datestampN source_linkN source_urlN toc_backlinksentryfootnote_backlinksK sectnum_xformKstrip_commentsNstrip_elements_with_classesN strip_classesN report_levelK halt_levelKexit_status_levelKdebugNwarning_streamN tracebackinput_encoding utf-8-siginput_encoding_error_handlerstrictoutput_encodingutf-8output_encoding_error_handlerjZerror_encodingutf-8error_encoding_error_handlerbackslashreplace language_codeenrecord_dependenciesNconfigN id_prefixhauto_id_prefixid dump_settingsNdump_internalsNdump_transformsNdump_pseudo_xmlNexpose_internalsNstrict_visitorN_disable_configN_sourcehÌ _destinationN _config_files]7/var/lib/git/docbuild/linux/Documentation/docutils.confafile_insertion_enabled raw_enabledKline_length_limitM'pep_referencesN pep_base_urlhttps://peps.python.org/pep_file_url_templatepep-%04drfc_referencesN rfc_base_url&https://datatracker.ietf.org/doc/html/ tab_widthKtrim_footnote_reference_spacesyntax_highlightlong smart_quotessmartquotes_locales]character_level_inline_markupdoctitle_xform docinfo_xformKsectsubtitle_xform image_loadinglinkembed_stylesheetcloak_email_addressessection_self_linkenvNubreporterNindirect_targets]substitution_defs}substitution_names}refnames}refids}(h]hajc]jYaj]jajf]j\aunameids}(j2hj1j.jjj jcjjjmjjljijjfjjj"jjjjjj)j&u nametypes}(j2j1jj jjmjljjj"jjj)uh}(hhj.hjjjcjdjjdjj'jij'jfjrjjrjjjj%jjj&ju footnote_refs} citation_refs} autofootnotes]autofootnote_refs]symbol_footnotes]symbol_footnote_refs] footnotes] citations]autofootnote_startKsymbol_footnote_startK id_counter collectionsCounter}jhKsRparse_messages]transform_messages](hsystem_message)}(hhh]h)}(hhh]h9Hyperlink target "stable-kernel-rules" is not referenced.}hjsbah}(h]h ]h"]h$]h&]uh1hhjubah}(h]h ]h"]h$]h&]levelKtypeINFOsourcehÌlineKuh1jubj)}(hhh]h)}(hhh]h.Hyperlink target "option-1" is not referenced.}hjsbah}(h]h ]h"]h$]h&]uh1hhjubah}(h]h ]h"]h$]h&]levelKtypejsourcehÌlineKAuh1jubj)}(hhh]h)}(hhh]h.Hyperlink target "option-2" is not referenced.}hjsbah}(h]h ]h"]h$]h&]uh1hhjubah}(h]h ]h"]h$]h&]levelKtypejsourcehÌlineKuh1jubj)}(hhh]h)}(hhh]h.Hyperlink target "option-3" is not referenced.}hj sbah}(h]h ]h"]h$]h&]uh1hhj ubah}(h]h ]h"]h$]h&]levelKtypejsourcehÌlineKuh1jube transformerN include_log] decorationNhhub.