From: Joe Perches <joe@perches.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Russell King - ARM Linux <linux@armlinux.org.uk>,
lkml <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: rfc: Updating SubmittingPatches with [RFC PATCH] and/or [WIP PATCH]
Date: Wed, 07 Sep 2016 12:47:41 -0700 [thread overview]
Message-ID: <1473277661.29864.25.camel@perches.com> (raw)
In-Reply-To: <20160907163854.GE4921@dell>
On Wed, 2016-09-07 at 17:38 +0100, Lee Jones wrote:
> On Wed, 07 Sep 2016, Joe Perches wrote:
[]
> > And another patch series prefix that could be used
> > instead of RFC is WIP.
> Certainly sounds reasonable. Is there a difference in the meaning?
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
+defects and you would like others to see the work to date use
+[WIP PATCH] before each patch subject.
11) Sign your work
next prev parent reply other threads:[~2016-09-07 19:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 13:03 [PATCH] mfd: ucb1x00: remove NO_IRQ check Arnd Bergmann
2016-09-06 13:17 ` Russell King - ARM Linux
2016-09-06 13:49 ` Arnd Bergmann
2016-09-06 15:45 ` Lee Jones
2016-09-06 16:28 ` Russell King - ARM Linux
2016-09-07 10:27 ` Lee Jones
2016-09-07 11:27 ` Russell King - ARM Linux
2016-09-07 12:48 ` Lee Jones
2016-09-07 13:44 ` Russell King - ARM Linux
2016-09-07 15:08 ` Lee Jones
2016-09-07 16:07 ` Russell King - ARM Linux
2016-09-07 16:27 ` Lee Jones
2016-09-07 16:36 ` Russell King - ARM Linux
[not found] ` <1473265954.29864.15.camel@perches.com>
[not found] ` <20160907163854.GE4921@dell>
2016-09-07 19:47 ` Joe Perches [this message]
2016-09-07 21:49 ` rfc: Updating SubmittingPatches with [RFC PATCH] and/or [WIP PATCH] Randy Dunlap
2016-09-14 19:03 ` Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1473277661.29864.25.camel@perches.com \
--to=joe@perches.com \
--cc=corbet@lwn.net \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.