change system file

hc

2024-10-09 244b2c5ca8b14627e4a17755e5922221e121c771

 kernel/Documentation/process/stable-kernel-rules.rst
..
..
@@ -35,12 +35,6 @@
35
35
 Procedure for submitting patches to the -stable tree
36
36
 ----------------------------------------------------
37
37
 
38
- - If the patch covers files in net/ or drivers/net please follow netdev stable
39
-   submission guidelines as described in
40
-   :ref:`Documentation/networking/netdev-FAQ.rst <netdev-FAQ>`
41
-   after first checking the stable networking queue at
42
-   https://patchwork.ozlabs.org/bundle/davem/stable/?series=&submitter=&state=*&q=&archive=
43
-   to ensure the requested patch is not already queued up.
44
38
  - Security patches should not be handled (solely) by the -stable review
45
39
    process but should follow the procedures in
46
40
    :ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>`.
..
..
@@ -101,9 +95,9 @@
101
95
 
102
96
     commit <sha1> upstream.
103
97
 
104
-Additionally, some patches submitted via Option 1 may have additional patch
105
-prerequisites which can be cherry-picked. This can be specified in the following
106
-format in the sign-off area:
98
+Additionally, some patches submitted via :ref:`option_1` may have additional
99
+patch prerequisites which can be cherry-picked. This can be specified in the
100
+following format in the sign-off area:
107
101
 
108
102
 .. code-block:: none
109
103
 
..
..
@@ -174,7 +168,16 @@
174
168
  - The finalized and tagged releases of all stable kernels can be found
175
169
    in separate branches per version at:
176
170
 
177
-	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
171
+	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
172
+
173
+ - The release candidate of all stable kernel versions can be found at:
174
+
175
+        https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/
176
+
177
+   .. warning::
178
+      The -stable-rc tree is a snapshot in time of the stable-queue tree and
179
+      will change frequently, hence will be rebased often. It should only be
180
+      used for testing purposes (e.g. to be consumed by CI systems).
178
181
 
179
182
 
180
183
 Review committee