db/fixup_kernel.sh: delete some impossible returns
[smatch.git] / Documentation / submitting-patches.md
blob5c4191bd933286706b8b9ee1d69c7c277ce2d498
1 Submitting patches
2 ==================
4 Sparse 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)
7 This document mostly focuses on the parts that might be different from the Linux
8 Kernel submitting process.
10 1. Git clone a sparse repository:
12         git clone git://git.kernel.org/pub/scm/devel/sparse/sparse.git
14 2. [Coding Style](https://www.kernel.org/doc/html/v4.12/process/coding-style.html) remains the same.
16 3. Sign off the patch.
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).
20    Notice that sparse uses the MIT License.
22 4. Smatch is built on top of Sparse but it is licensed under the GPLv2+ the
23    git repostories are:
25         https://github.com/error27/smatch
26         https://repo.or.cz/w/smatch.git
28    They are identical mirrors so it doesn't matter which you use.
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.