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

Message-ID: <CABGNeczK4Jdw5aAoT62-SZsKrYTTKh+pUgMZWcCa59c5YqZgXg@mail.gmail.com>
Date:   Mon, 12 Mar 2018 16:01:08 -0700
From:   Joe Smith <codesoldier1@...il.com>
To:     linux-kernel@...r.kernel.org
Subject: Guidelines for Submitting an RFC PATCH

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.

Regards

-- 
JS