linux-kernel - [075/264] Update email address for stable patch submission

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 09 Nov 2011 13:32:02 -0800
From:	Greg KH <gregkh@...e.de>
To:	linux-kernel@...r.kernel.org, stable@...r.kernel.org
Cc:	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	alan@...rguk.ukuu.org.uk, Josh Boyer <jwboyer@...hat.com>
Subject: [075/264] Update email address for stable patch submission

3.1-stable review patch.  If anyone has any objections, please let me know.

------------------

From: Josh Boyer <jwboyer@...hat.com>

commit 5fa224295f0e0358c8bc0e5390702338df889def upstream.

The stable@...nel.org email address has been replaced with the
stable@...r.kernel.org mailing list.  Change the stable kernel rules to
reference the new list instead of the semi-defunct email alias.

Signed-off-by: Josh Boyer <jwboyer@...hat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@...e.de>

---
 Documentation/stable_kernel_rules.txt |   14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

--- a/Documentation/stable_kernel_rules.txt
+++ b/Documentation/stable_kernel_rules.txt
@@ -24,10 +24,10 @@ Rules on what kind of patches are accept
 Procedure for submitting patches to the -stable tree:
 
  - Send the patch, after verifying that it follows the above rules, to
-   stable@...nel.org.  You must note the upstream commit ID in the changelog
-   of your submission.
+   stable@...r.kernel.org.  You must note the upstream commit ID in the
+   changelog of your submission.
  - To have the patch automatically included in the stable tree, add the tag
-     Cc: stable@...nel.org
+     Cc: stable@...r.kernel.org
    in the sign-off area. Once the patch is merged it will be applied to
    the stable tree without anything else needing to be done by the author
    or subsystem maintainer.
@@ -35,10 +35,10 @@ Procedure for submitting patches to the
    cherry-picked than this can be specified in the following format in
    the sign-off area:
 
-     Cc: <stable@...nel.org> # .32.x: a1f84a3: sched: Check for idle
-     Cc: <stable@...nel.org> # .32.x: 1b9508f: sched: Rate-limit newidle
-     Cc: <stable@...nel.org> # .32.x: fd21073: sched: Fix affinity logic
-     Cc: <stable@...nel.org> # .32.x
+     Cc: <stable@...r.kernel.org> # .32.x: a1f84a3: sched: Check for idle
+     Cc: <stable@...r.kernel.org> # .32.x: 1b9508f: sched: Rate-limit newidle
+     Cc: <stable@...r.kernel.org> # .32.x: fd21073: sched: Fix affinity logic
+     Cc: <stable@...r.kernel.org> # .32.x
     Signed-off-by: Ingo Molnar <mingo@...e.hu>
 
    The tag sequence has the meaning of:


--
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/