Skip to content

Commit cc8246d

Browse files
xypronJonathan Corbet
authored andcommitted
docs: dev-tools: coccinelle: underlines
Underline lengths should match the lengths of headings to avoid build warnings with Sphinx. Signed-off-by: Heinrich Schuchardt <[email protected]> Acked-by: Julia Lawall <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Jonathan Corbet <[email protected]>
1 parent e35b5a4 commit cc8246d

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

Documentation/dev-tools/coccinelle.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ many uses in kernel development, including the application of complex,
1414
tree-wide patches and detection of problematic programming patterns.
1515

1616
Getting Coccinelle
17-
-------------------
17+
------------------
1818

1919
The semantic patches included in the kernel use features and options
2020
which are provided by Coccinelle version 1.0.0-rc11 and above.
@@ -56,7 +56,7 @@ found at:
5656
https://github.com/coccinelle/coccinelle/blob/master/install.txt
5757

5858
Supplemental documentation
59-
---------------------------
59+
--------------------------
6060

6161
For supplemental documentation refer to the wiki:
6262

@@ -128,7 +128,7 @@ To enable verbose messages set the V= variable, for example::
128128
make coccicheck MODE=report V=1
129129

130130
Coccinelle parallelization
131-
---------------------------
131+
--------------------------
132132

133133
By default, coccicheck tries to run as parallel as possible. To change
134134
the parallelism, set the J= variable. For example, to run across 4 CPUs::
@@ -333,7 +333,7 @@ as an example if requiring at least Coccinelle >= 1.0.5::
333333
// Requires: 1.0.5
334334

335335
Proposing new semantic patches
336-
-------------------------------
336+
------------------------------
337337

338338
New semantic patches can be proposed and submitted by kernel
339339
developers. For sake of clarity, they should be organized in the

0 commit comments

Comments
 (0)