Searched full:indentation (Results 1 – 21 of 21) sorted by relevance
| /Documentation/devicetree/bindings/ |
| D | .yamllint | 29 comments-indentation: disable
40 indentation:
|
| D | dts-coding-style.rst | 165 Indentation chapter
168 1. Use indentation according to Documentation/process/coding-style.rst.
|
| D | writing-schema.rst | 136 Use YAML coding style (two-space indentation). For DTS examples in the schema,
137 preferred is four-space indentation.
|
| D | example-schema.yaml | 25 indentation less than the first line of the literal block. Lines also cannot
256 # Any includes used have to be explicitly included. Use 4-space indentation.
|
| /Documentation/process/ |
| D | coding-style.rst | 18 1) Indentation
26 Rationale: The whole idea behind indentation is to clearly define where
29 how the indentation works if you have large indentations.
34 more than 3 levels of indentation, you're screwed anyway, and should fix
41 The preferred way to ease multiple indentation levels in a switch statement is
93 used for indentation, and the above example is deliberately broken.
294 ``smart`` indentation will insert whitespace at the beginning of new lines as
451 complexity and indentation level of that function. So, if you have a
666 (c-label-minimum-indentation . 0)
726 Some basic editor settings, such as indentation and line endings, will be
[all …]
|
| D | 4.Coding.rst | 69 Some basic editor settings, such as indentation and line endings, will be
|
| D | submitting-patches.rst | 721 indentation). (``git`` generates appropriate diffstats by default.)
|
| /Documentation/dev-tools/ |
| D | checkpatch.rst | 652 Indentation and Line Breaks
658 spaces are never used for indentation.
660 See: https://www.kernel.org/doc/html/latest/process/coding-style.html#indentation
663 Indentation with 6 or more tabs usually indicate overly indented
666 It is suggested to refactor excessive indentation of
692 See: https://www.kernel.org/doc/html/latest/process/coding-style.html#indentation
|
| D | ktap.rst | 195 indentation is two spaces: " ". The indentation should begin at the version
|
| /Documentation/maintainer/ |
| D | pull-requests.rst | 80 trivial formatting (the whole indentation and quoting etc), but
|
| /Documentation/driver-api/media/ |
| D | maintainer-entry-profile.rst | 170 to less indentation, shorter variable or function names and last but not
|
| /Documentation/admin-guide/pm/ |
| D | cpufreq_drivers.rst | 9 with the original white space formatting and indentation preserved, except for
|
| /Documentation/rust/ |
| D | coding-guidelines.rst | 22 style is followed. For instance, 4 spaces are used for indentation rather
|
| /Documentation/scsi/ |
| D | ChangeLog.lpfc | 36 * Fixed a bunch of mixed tab/space indentation.
270 * Fixed some trailing whitespaces, spaces used for indentation and
432 indentation.
1767 * Many indentation/whitespace fixes.
1845 * Several small indentation cleanups.
|
| D | ChangeLog.megaraid | 549 iii. Miscellaneous indentation and goto/label fixes.
|
| /Documentation/kbuild/ |
| D | kconfig-language.rst | 237 the indentation level, this means it ends at the first line which has
238 a smaller indentation than the first line of the help text.
|
| /Documentation/doc-guide/ |
| D | kernel-doc.rst | 50 overview kernel-doc comments may be placed anywhere at the top indentation
|
| /Documentation/translations/zh_CN/process/ |
| D | coding-style.rst | 606 (c-label-minimum-indentation . 0)
|
| /Documentation/translations/zh_TW/process/ |
| D | coding-style.rst | 609 (c-label-minimum-indentation . 0)
|
| /Documentation/translations/it_IT/process/ |
| D | coding-style.rst | 670 (c-label-minimum-indentation . 0)
|
| /Documentation/translations/sp_SP/process/ |
| D | coding-style.rst | 697 (c-label-minimum-indentation . 0)
|