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

Message-ID: <20160914130349.7ee76c3c@lwn.net>
Date:   Wed, 14 Sep 2016 13:03:49 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Joe Perches <joe@...ches.com>
Cc:     Lee Jones <lee.jones@...aro.org>,
        Russell King - ARM Linux <linux@...linux.org.uk>,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: rfc: Updating SubmittingPatches with [RFC PATCH] and/or [WIP
 PATCH]

On Wed, 07 Sep 2016 12:47:41 -0700
Joe Perches <joe@...ches.com> wrote:

> +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
> +defects and you would like others to see the work to date use
> +[WIP PATCH] before each patch subject.

It would be good to apply Randy's typo fix here.

Also, though, if we're going to do this, it's probably worth mentioning
that one should not expect patches marked RFC to be applied, and that
some maintainers may not even seriously review them. That seems to
surprise people regularly.

jon