Networking is once again "special", so at least document
how it's working today in the hope that doing so makes
less work for all that actually read the documentation.
Signed-off-by: Joe Perches <joe@xxxxxxxxxxx>
---
On Thu, 19 Sep 2013, David Miller wrote:
> Secondly, CC:'ing stable is not the correct way to submit networking
> patches for -stable inclusion. You simply ask me to queue them up
> for -stable explicitly instead.
Documentation/stable_kernel_rules.txt | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/stable_kernel_rules.txt b/Documentation/stable_kernel_rules.txt
index b0714d8..a2d6da0 100644
--- a/Documentation/stable_kernel_rules.txt
+++ b/Documentation/stable_kernel_rules.txt
@@ -29,6 +29,11 @@ Rules on what kind of patches are accepted, and which ones are not, into the
Procedure for submitting patches to the -stable tree:
+ - The networking tree (net/ and drivers/net/) is 'special' and doesn't
+ follow the rules below. Don't send or cc: patches for the -stable tree to
+ stable@xxxxxxxxxxxxxxx. Don't mark them stable. Just send the patches to
+ netdev@xxxxxxxxxxxxxxx and let the networking maintainer decide what to do
+ with them.
- Send the patch, after verifying that it follows the above rules, to
stable@xxxxxxxxxxxxxxx. You must note the upstream commit ID in the
changelog of your submission, as well as the kernel version you wish
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
