[PATCH v4] docs: stable-kernel-rules: drop rules the stable trees do not apply
From: Sasha Levin
Date: Tue Oct 20 2026 - 11:24:49 EST
The stable trees do not apply the 100 line limit or the exclusion of
theoretical issues, and they require a fix to be correct and tested
rather than obviously correct. Drop those rules.
Assisted-by: LLM
Signed-off-by: Sasha Levin <sashal@xxxxxxxxxx>
Reviewed-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
Acked-by: SJ Park <sj@xxxxxxxxxx>
---
v4:
- Split out of the agents skills series, where this was patch 3/7 of v3:
https://lore.kernel.org/r/20261016152828.3765695-4-sashal@xxxxxxxxxx
- No other changes.
Documentation/process/stable-kernel-rules.rst | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/Documentation/process/stable-kernel-rules.rst b/Documentation/process/stable-kernel-rules.rst
index edf90bbe30f43..625c1b5b0e16b 100644
--- a/Documentation/process/stable-kernel-rules.rst
+++ b/Documentation/process/stable-kernel-rules.rst
@@ -7,8 +7,7 @@ Rules on what kind of patches are accepted, and which ones are not, into the
"-stable" tree:
- It or an equivalent fix must already exist in Linux mainline (upstream).
-- It must be obviously correct and tested.
-- It cannot be bigger than 100 lines, with context.
+- It must be correct and tested.
- It must follow the
:ref:`Documentation/process/submitting-patches.rst <submittingpatches>`
rules.
@@ -24,9 +23,6 @@ Rules on what kind of patches are accepted, and which ones are not, into the
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).
base-commit: 3857c2fe5449541e24afc5efdb0f81a8a8f9a3a0
--
2.53.0