blob: 0bb38650e49bf59f56e20032a5fcf0e70ff53635 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
#
# Configure how the Linux checkpatch script should be invoked in the context of
# the TFTF source tree.
#
# This is not Linux so don't expect a Linux tree!
--no-tree
# We don't mandate 'Signed-off-by' line in TFTF
--no-signoff
# This clarifes the lines indications in the report.
#
# E.g.:
# Without this option, we have the following output:
# #333: FILE: drivers/arm/gic/arm_gic_v2v3.c:160:
# So we have 2 lines indications (333 and 160), which is confusing.
# We only care about the position in the source file.
#
# With this option, it becomes:
# drivers/arm/gic/arm_gic_v2v3.c:160:
--showfile
#
# Ignore the following message types, as they don't necessarily make sense in
# the context of the TFTF.
#
# COMPLEX_MACRO generates false positives.
--ignore COMPLEX_MACRO
# TFTF commit messages are expected to have a Gerrit Change-Id.
--ignore GERRIT_CHANGE_ID
# FILE_PATH_CHANGES reports this kind of message:
# "added, moved or deleted file(s), does MAINTAINERS need updating?"
# We do not use this MAINTAINERS file process in TFTF.
--ignore FILE_PATH_CHANGES
# AVOID_EXTERNS reports this kind of messages:
# "externs should be avoided in .c files"
# We don't follow this convention in TFTF.
--ignore AVOID_EXTERNS
# NEW_TYPEDEFS reports this kind of messages:
# "do not add new typedefs"
# We allow adding new typedefs in TFTF.
--ignore NEW_TYPEDEFS
# VOLATILE reports this kind of messages:
# "Use of volatile is usually wrong: see Documentation/volatile-considered-harmful.txt"
# We allow the usage of the volatile keyword in TFTF.
--ignore VOLATILE
|
