1Submitting patches: the sparse version 2====================================== 3 4Sparse uses a patch submit process similar to the Linux Kernel 5[Submitting Patches](https://www.kernel.org/doc/html/v4.12/process/submitting-patches.html) 6 7This document mostly focuses on the parts that might be different from the Linux 8Kernel submitting process. 9 101. Git clone a sparse repository: 11 12 git clone git://git.kernel.org/pub/scm/devel/sparse/sparse.git 13 142. [Coding Style](https://www.kernel.org/doc/html/v4.12/process/coding-style.html) remains the same. 15 163. Sign off the patch. 17 18 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). 19 20 Notice that sparse uses the MIT License. 21 224. Smatch is built on top of Sparse but it is licensed under the GPLv2+ the 23 git repostories are: 24 25 https://github.com/error27/smatch 26 https://repo.or.cz/w/smatch.git 27 28 They are identical mirrors so it doesn't matter which you use. 29 30 Send patches for to Smatch to <smatch@vger.kernel.org>. If the code is 31 shared with both Sparse and Smatch then please send it to the Sparse 32 mailing list instead <linux-sparse@vger.kernel.org> and I will pick it up 33 from there. 34 35