public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: David Miller <davem@davemloft.net>
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
	Mikulas Patocka <mpatocka@redhat.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Rob Landley <rob@landley.net>,
	linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] stable_kernel_rules.txt: Exclude networking from stable rules
Date: Thu, 19 Sep 2013 11:31:14 -0700	[thread overview]
Message-ID: <1379615474.22168.13.camel@joe-AO722> (raw)
In-Reply-To: <alpine.LRH.2.02.1309191359300.12162@file01.intranet.prod.int.rdu2.redhat.com>

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@perches.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@vger.kernel.org.  Don't mark them stable.  Just send the patches to
+   netdev@vger.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@vger.kernel.org.  You must note the upstream commit ID in the
    changelog of your submission, as well as the kernel version you wish




  parent reply	other threads:[~2013-09-19 18:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-19 16:33 [PATCH] skge: fix broken driver Mikulas Patocka
2013-09-19 17:56 ` David Miller
2013-09-19 18:04   ` Mikulas Patocka
2013-09-19 18:07     ` David Miller
2013-09-19 18:16     ` Igor Gnatenko
2013-09-19 18:29       ` Mikulas Patocka
2013-09-19 21:32         ` Francois Romieu
2013-09-20 14:32           ` Mikulas Patocka
2013-09-20 15:35             ` Igor Gnatenko
2013-09-20 21:38             ` Francois Romieu
2013-09-23 14:58               ` Mikulas Patocka
2013-09-19 18:31     ` Joe Perches [this message]
2013-09-19 21:32       ` [PATCH] stable_kernel_rules.txt: Exclude networking from stable rules Francois Romieu
2013-09-19 21:45         ` Joe Perches
2013-09-19 22:37           ` Francois Romieu
2013-09-20 14:54       ` Joe Perches
2013-09-20 15:59         ` David Miller
2013-09-22 18:51       ` Christoph Hellwig
2013-09-23 20:34         ` Joe Perches
2013-09-24  8:48           ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1379615474.22168.13.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=stephen@networkplumber.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox