11f5207b7SJohn LevonSubmitting patches: the sparse version 21f5207b7SJohn Levon====================================== 31f5207b7SJohn Levon 41f5207b7SJohn LevonSparse uses a patch submit process similar to the Linux Kernel 51f5207b7SJohn Levon[Submitting Patches](https://www.kernel.org/doc/html/v4.12/process/submitting-patches.html) 61f5207b7SJohn Levon 71f5207b7SJohn LevonThis document mostly focuses on the parts that might be different from the Linux 81f5207b7SJohn LevonKernel submitting process. 91f5207b7SJohn Levon 101f5207b7SJohn Levon1. Git clone a sparse repository: 111f5207b7SJohn Levon 121f5207b7SJohn Levon git clone git://git.kernel.org/pub/scm/devel/sparse/sparse.git 131f5207b7SJohn Levon 141f5207b7SJohn Levon2. [Coding Style](https://www.kernel.org/doc/html/v4.12/process/coding-style.html) remains the same. 151f5207b7SJohn Levon 161f5207b7SJohn Levon3. Sign off the patch. 171f5207b7SJohn Levon 181f5207b7SJohn Levon 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). 191f5207b7SJohn Levon 201f5207b7SJohn Levon Notice that sparse uses the MIT License. 211f5207b7SJohn Levon 22*b3263c98SJohn Levon4. Smatch is built on top of Sparse but it is licensed under the GPLv2+ the 23*b3263c98SJohn Levon git repostories are: 24*b3263c98SJohn Levon 25*b3263c98SJohn Levon https://github.com/error27/smatch 26*b3263c98SJohn Levon https://repo.or.cz/w/smatch.git 27*b3263c98SJohn Levon 28*b3263c98SJohn Levon They are identical mirrors so it doesn't matter which you use. 29*b3263c98SJohn Levon 30*b3263c98SJohn Levon Send patches for to Smatch to <smatch@vger.kernel.org>. If the code is 31*b3263c98SJohn Levon shared with both Sparse and Smatch then please send it to the Sparse 32*b3263c98SJohn Levon mailing list instead <linux-sparse@vger.kernel.org> and I will pick it up 33*b3263c98SJohn Levon from there. 34*b3263c98SJohn Levon 35