lkml.org 
[lkml]   [2008]   [Feb]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
Date
From
Subject[PATCH] stable_kernel_rules: fix must already be in mainline
On  7 Feb, Greg KH wrote:
> On Fri, Feb 08, 2008 at 12:24:57PM +1100, David Chinner wrote:
>> On Thu, Feb 07, 2008 at 05:12:30PM -0800, Greg KH wrote:
>> > On Fri, Feb 08, 2008 at 11:44:30AM +1100, David Chinner wrote:
>> > > We've had multiple reports of it, and multiple confirmations that
>> > > the patch in the link above fixes the problem.....
>> >
>> > I didn't think it was in Linus's tree yet. Is it?
>>
>> Not yet - it's in the pipeline. I'll see if that can be sped
>> up (someone else usually takes care of the pushes to Linus).
>
> Then we did our job right and didn't take it :)
>
> Please resend it after it gets into Linus's tree, not before, I'm really
> tired of checking for these things constantly...

----------------
From: Stefan Richter <stefanr@s5r6.in-berlin.de>

stable_kernel_rules: fix must already be in mainline

Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
---
Documentation/stable_kernel_rules.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)

Index: linux-2.6.24-git19/Documentation/stable_kernel_rules.txt
===================================================================
--- linux-2.6.24-git19.orig/Documentation/stable_kernel_rules.txt
+++ linux-2.6.24-git19/Documentation/stable_kernel_rules.txt
@@ -16,8 +16,9 @@ Rules on what kind of patches are accept
race can be exploited is also provided.
- It cannot contain any "trivial" fixes in it (spelling changes,
whitespace cleanups, etc).
- - It must be accepted by the relevant subsystem maintainer.
- It must follow the Documentation/SubmittingPatches rules.
+ - It or an equivalent fix must already exist in Linus' tree. Quote the
+ respective commit ID in Linus' tree in your patch submission to -stable.


Procedure for submitting patches to the -stable tree:
@@ -28,7 +29,7 @@ Procedure for submitting patches to the
queue, or a NAK if the patch is rejected. This response might take a few
days, according to the developer's schedules.
- If accepted, the patch will be added to the -stable queue, for review by
- other developers.
+ other developers and by the relevant subsystem maintainer.
- Security patches should not be sent to this alias, but instead to the
documented security@kernel.org address.

--
Stefan Richter
-=====-==--- --=- -=---
http://arcgraph.de/sr/


\
 
 \ /
  Last update: 2008-02-08 23:37    [W:0.104 / U:2.468 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site