linux-kernel - Re: Guidelines for Submitting an RFC 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: <20180316101633.GA2378@amd>
Date:   Fri, 16 Mar 2018 11:16:33 +0100
From:   Pavel Machek <pavel@....cz>
To:     Joe Smith <codesoldier1@...il.com>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: Guidelines for Submitting an RFC PATCH

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

Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)