From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Guidelines for Submitting an RFC PATCH
Date: Tue, 13 Mar 2018 08:28:05 +0100 [thread overview]
Message-ID: <20180313072805.GA717@kroah.com> (raw)
In-Reply-To: <CABGNecyuhHD9z6beRceGGb6nMR2gPLZ_xXBy2t4xjRUWgCN6uw@mail.gmail.com>
On Mon, Mar 12, 2018 at 03:48:52PM -0700, Joe Smith wrote:
> Thanks, Greg and Valdis.
> An RFC patch by definition is not intended for submission. In cases
> where the design is involved and the developer needs early input, why
> go through all the hassle. The community could say I do not like it
> and the whole effort would be useless. Once there is agreement then I
> can see the need for all patches to be conformant.
What do you mean exactly by "conformant"? Why would you not write
"conformant" patches to start with? You don't want to have to do double
the work by writing code in the wrong style first, and then having to go
back and rewrite it.
Anyway, be careful about RFC patches, you want to make it as easy as
possible for others to review your work, so don't give anyone an excuse
to _not_ read it.
thanks,
greg k-h
next prev parent reply other threads:[~2018-03-13 7:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 19:26 Guidelines for Submitting an RFC PATCH Joe Smith
2018-03-12 19:56 ` valdis.kletnieks at vt.edu
2018-03-12 20:42 ` Greg KH
2018-03-12 22:48 ` Joe Smith
2018-03-13 7:28 ` Greg KH [this message]
2018-03-13 15:52 ` Joe Smith
2018-03-13 18:10 ` valdis.kletnieks at vt.edu
2018-03-13 22:01 ` Joe Smith
2018-03-13 18:35 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2018-03-12 23:01 Joe Smith
2018-03-16 10:16 ` Pavel Machek
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=20180313072805.GA717@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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.