linux-kernel - [PATCH] stable_kernel_rules.txt: Exclude networking from stable rules

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 19 Sep 2013 11:31:14 -0700
From:	Joe Perches <joe@...ches.com>
To:	David Miller <davem@...emloft.net>
Cc:	stephen@...workplumber.org, netdev@...r.kernel.org,
	Mikulas Patocka <mpatocka@...hat.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Rob Landley <rob@...dley.net>, linux-doc@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: [PATCH] stable_kernel_rules.txt: Exclude networking from stable
 rules

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@...ches.com>
---
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@...r.kernel.org.  Don't mark them stable.  Just send the patches to
+   netdev@...r.kernel.org and let the networking maintainer decide what to do
+   with them.
  - Send the patch, after verifying that it follows the above rules, to
    stable@...r.kernel.org.  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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/