Reference to the linux kernel patches submitting process and difference to sparse. Signed-off-by: Christopher Li <sparse@xxxxxxxxxxx> --- Documentation/submitting-patches.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 Documentation/submitting-patches.md diff --git a/Documentation/submitting-patches.md b/Documentation/submitting-patches.md new file mode 100644 index 0000000..412072e --- /dev/null +++ b/Documentation/submitting-patches.md @@ -0,0 +1,21 @@ +Submitting patches: the sparse version +====================================== + +Sparse uses a patch submit process similar to the Linux Kernel +[Submitting Patches](https://www.kernel.org/doc/html/v4.12/process/submitting-patches.html) + +This document mostly focuses on the parts that might be different from the Linux +Kernel submitting process. + +1. Git clone a sparse repository: + + git clone git://git.kernel.org/pub/scm/devel/sparse/sparse.git + +2. [Coding Style](https://www.kernel.org/doc/html/v4.12/process/coding-style.html) remains the same. + +3. Sign off the patch. + + The usage of the Signed-off-by tag is the same as [Linux Kernel Sign your work](https://www.kernel.org/doc/html/v4.12/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin). + + Notice that sparse uses the MIT License. + -- 2.13.3 -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
