Project

General

Profile

Linting » History » Version 3

osmith, 06/17/2021 08:27 AM

1 1 osmith
h1. Linting
2
3
Patches submitted to [[Gerrit]] are automatically linted to ensure patches follow our [[coding standards]] and to catch common spelling errors. Jenkins runs @checkpatch.pl@ from the Linux kernel (with an Osmocom specific configuration) against the diff of the current patch.
4
5 2 osmith
h2. Run locally
6 1 osmith
7 2 osmith
Go to the directory above your Osmocom sources, then run the following:
8
9
<pre>
10
$ git clone https://git.osmocom.org/osmo-ci
11
$ cd libosmocore
12
$ ../osmo-ci/lint/lint_diff.sh
13
</pre>
14
15
h2. Pre-commit hook
16
17 1 osmith
The linting script is very fast, it makes sense to configure it locally as pre-commit hook. Then it will run whenever attempting to @git commit@.
18
19 3 osmith
After cloning osmo-ci.git (see above), go to the directory above your Osmocom sources again and run the following. Replace libosmocore with any checked out Osmocom project.
20 1 osmith
<pre>
21
$ ln -sv $PWD/osmo-ci/lint/lint_diff.sh libosmocore/.git/hooks/pre-commit
22
</pre>
23
24
h2. Osmocom specific configuration
25
26
Find the Osmocom specific configuration in @osmo-ci/lint/checkpatch/checkpatch_osmo.sh@.
27
28
If you see the script generating errors with checks that don't apply for Osmocom code (see the ignores and excludes already in the script), please submit a patch against osmo-ci.git that disables this specific check.
29
30
h2. Testing
31
32
Run @osmo-ci/lint/lint_all.sh@ in a git repository to run the script against all files in that repository and to report the total amount of errors. It is also possible to run only a specific check of @checkpatch.pl@ by passing it as argument. For example:
33
34
<pre>
35
$ cd libosmocore
36
$ ../osmo-ci/lint/lint_all.sh CODE_INDENT
37
</pre>
38
39
h2. See also
40
41
* #5087
Add picture from clipboard (Maximum size: 48.8 MB)