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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 26 Mar 2015 09:45:45 -0700
From:	David Daney <ddaney.cavm@...il.com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	David Daney <david.daney@...ium.com>
Subject: Re: [PATCH] stable_kernel_rules: Add clause about specification of
 kernel versions to patch.

On 03/25/2015 07:05 AM, Greg Kroah-Hartman wrote:
> On Mon, Feb 09, 2015 at 03:39:23PM -0800, David Daney wrote:
>> From: David Daney <david.daney@...ium.com>
>>
>> Signed-off-by: David Daney <david.daney@...ium.com>
>> ---
>>   Documentation/stable_kernel_rules.txt | 10 ++++++++++
>>   1 file changed, 10 insertions(+)
>>
>> diff --git a/Documentation/stable_kernel_rules.txt b/Documentation/stable_kernel_rules.txt
>> index aee73e7..82c097a 100644
>> --- a/Documentation/stable_kernel_rules.txt
>> +++ b/Documentation/stable_kernel_rules.txt
>> @@ -41,6 +41,16 @@ Procedure for submitting patches to the -stable tree:
>>      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.
>> + - The kernel versions, to which the patch should be applied, can be
>> +   specified in the following format in the sign-off area:
>> +
>> +     Cc:  <stable@...r.kernel.org> # 3.3.x
>> +
>> +   The tag has the meaning of:
>> +     git cherry-pick <this commit>
>> +
>> +   For each "-stable" tree starting with the specified version.
>> +
>>    - If the patch requires other patches as prerequisites which can be
>>      cherry-picked, then this can be specified in the following format in
>>      the sign-off area:
>> --
>> 1.7.11.7
>
> This doesn't apply to the tree, what kernel version did you make it
> against?  Can you make it against Linus's latest tree and resend it?
>

I just sent out a new version.

David Daney

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ