linux-kernel - Re: rfc: Updating SubmittingPatches with [RFC PATCH] and/or [WIP PATCH]

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, 7 Sep 2016 14:49:17 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Joe Perches <joe@...ches.com>, Lee Jones <lee.jones@...aro.org>
Cc:     Russell King - ARM Linux <linux@...linux.org.uk>,
        lkml <linux-kernel@...r.kernel.org>,
        Jonathan Corbet <corbet@....net>
Subject: Re: rfc: Updating SubmittingPatches with [RFC PATCH] and/or [WIP
 PATCH]

On 09/07/16 12:47, Joe Perches wrote:

> Request for Comment and Work In Progress differences:
> 
> Maybe add something like this to Documentation/SubmittingPatches
> ---
>  Documentation/SubmittingPatches | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> index 8c79f1d..aa76057 100644
> --- a/Documentation/SubmittingPatches
> +++ b/Documentation/SubmittingPatches
> @@ -404,6 +404,12 @@ convention to prefix your subject line with [PATCH].  This 
>  and other kernel developers more easily distinguish patches from other
>  e-mail discussions.
>  
> +If the patch or patch series is just a proposal to garner comments
> +use [RFC PATCH] before each patch subject.
> +
> +If the patch or patch seriies is incomplete or possibly contains known

                         series

> +defects and you would like others to see the work to date use
> +[WIP PATCH] before each patch subject.
>  
>  
>  11) Sign your work
> 


-- 
~Randy