Lines Matching full:should

12 In normal conditions, please name directories in lower-case. Directories should
13 have descriptive names. For example, the port of a chip should be composed of
15 should stand for what the component does.
35 The symbol should begin and end with "__" to avoid naming collision. The words
36 of the file name should be connected by "_".
41 In every header file, there should be copyright information and Change Log
71 Braces should have their own lines and the members should be defines with
74 The names of type defines such like structure types should be the structure name
97 upper application should be declared in header files. If the function don't have
98 parameters, it should be declared as void:
106 comments should describe what does the code do. And it should describe how the
107 complicated algorithm works. Comments to statements should be placed before them
114 other special meanings, the indent should begin right after "{":
121 The only one exception is switch. In switch-case statements, "case" should be
130 "case" is aligned with "switch", the following code block should be indented.
135 For ease of reading, it is advised that braces should occupy the whole line
146 There should be a space before parentheses when it's not a function call. For
159 In expressions, there should be a space between most binary and ternary
180 Logging should be off by default and can be turned on by a switch(e.g. a
181 variable or a macro). When logging, it should be easy to understand and easy to
187 Functions in kernel should be K.I.S.S. If the function is too long, you should