From: Pavel Machek <pavel@ucw.cz>
To: Joe Smith <codesoldier1@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Guidelines for Submitting an RFC PATCH
Date: Fri, 16 Mar 2018 11:16:33 +0100 [thread overview]
Message-ID: <20180316101633.GA2378@amd> (raw)
In-Reply-To: <CABGNeczK4Jdw5aAoT62-SZsKrYTTKh+pUgMZWcCa59c5YqZgXg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
On Mon 2018-03-12 16:01:08, Joe Smith wrote:
> Hi All,
>
> What are the guidelines for submitting an RFC patch? If a developer
> wants to get early input on a design is it fine to submit a patch that
> is in reasonable shape but does not fully meets the requirements of a
> regular patch, for example, the patch consists of a series of patches,
> it only compiles when all patches in the series are applied. Going
> through the process of meeting all the patch requirements for an RFC
> patch seems too much.
There are not many guidelines for that. Just mark it RFC :-).
Series that only compiles when full would be fine for example. (But
you may get complains from 0 day testing bots, not sure).
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2018-03-16 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 23:01 Guidelines for Submitting an RFC PATCH Joe Smith
2018-03-16 10:16 ` Pavel Machek [this message]
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=20180316101633.GA2378@amd \
--to=pavel@ucw.cz \
--cc=codesoldier1@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox