Searched full:statement (Results 1 – 25 of 254) sorted by relevance
1234567891011
| /linux-5.10/arch/mips/include/asm/ |
| D | compiler.h | 17 * that can lead to instructions from beyond an unreachable statement being
18 * incorrectly reordered into earlier delay slots if the unreachable statement
19 * is the only content of a case in a switch statement. This can lead to
35 * We work around both of these issues by placing a volatile asm statement,
39 * The .insn statement is required to ensure that any branches to the
40 * statement, which sadly must be kept due to the asm statement, are known to
|
| /linux-5.10/Documentation/doc-guide/ |
| D | parse-headers.rst | 101 The ignore or replace statement will apply to ioctl definitions like:
109 The ignore or replace statement will apply to any other #define found
116 The ignore or replace statement will apply to typedef statements at C_FILE.
122 The ignore or replace statement will apply to the name of struct statements
129 The ignore or replace statement will apply to the name of enum statements
136 The ignore or replace statement will apply to the name of enum value
142 also be explicitly defined at the replace statement.
|
| /linux-5.10/scripts/coccinelle/iterators/ |
| D | for_each_child.cocci | 2 // Adds missing of_node_put() before return/break/goto statement within a for_each iterator for chi…
24 statement S;
56 statement S;
85 statement S,S2;
118 statement S,S2;
148 statement S;
186 statement S, S2;
217 statement S2;
241 statement S,S2;
275 statement S2;
|
| D | list_entry_update.cocci | 30 statement S;
42 statement S;
|
| D | device_node_continue.cocci | 28 statement S;
60 statement S;
|
| /linux-5.10/scripts/coccinelle/api/alloc/ |
| D | zalloc-simple.cocci | 34 statement S;
51 statement S;
134 statement S;
148 statement S;
178 statement S;
208 statement S;
238 statement S;
268 statement S;
298 statement S;
328 statement S;
[all …]
|
| D | pool_zalloc-simple.cocci | 22 statement S;
36 statement S;
47 statement S;
62 statement S;
|
| /linux-5.10/scripts/coccinelle/null/ |
| D | deref_null.cocci | 44 statement S1,S2;
57 statement S1,S2,S3,S4;
118 statement S1,S2,S3,S4;
178 statement S1,S2,S3,S4;
240 statement S1,S2;
251 statement S1,S2,S3,S4;
|
| D | kmerr.cocci | 33 statement S;
49 statement S;
|
| /linux-5.10/scripts/coccinelle/api/ |
| D | kstrdup.cocci | 20 statement S;
33 statement S;
50 statement S;
63 statement S;
|
| D | memdup.cocci | 38 statement S;
49 statement S;
|
| D | memdup_user.cocci | 76 statement S1,S2;
89 statement S1,S2;
|
| /linux-5.10/drivers/media/dvb-frontends/drx39xyj/ |
| D | drx_dap_fasi.h | 99 *; /* illegal statement to force compiler error */
202 *; /* illegal statement to force compiler error */
205 *; /* illegal statement to force compiler error */
210 *; /* illegal statement to force compiler error */
213 *; /* illegal statement to force compiler error */
226 *; /* illegal statement to force compiler error */
232 *; /* illegal statement to force compiler error */
|
| /linux-5.10/Documentation/process/ |
| D | coding-style.rst | 41 The preferred way to ease multiple indentation levels in a switch statement is
118 This applies to all non-function statement blocks (if, switch, for,
150 the cases where it is followed by a continuation of the same statement,
151 ie a ``while`` in a do-statement or an ``else`` in an if-statement, like
180 Do not unnecessarily use braces where a single statement will do.
196 This does not apply if only one branch of a conditional statement is a single
197 statement; in the latter case use braces in both branches:
208 Also, use braces when a loop contains more than a single simple statement:
437 case-statement, where you have to do lots of small things for a lot of
478 Albeit deprecated by some people, the equivalent of the goto statement is
[all …]
|
| D | index.rst | 32 kernel-enforcement-statement
33 kernel-driver-statement
|
| D | kernel-driver-statement.rst | 3 Kernel Driver Statement
6 Position Statement on Linux Kernel Modules
|
| /linux-5.10/Documentation/trace/ |
| D | tracepoints.rst | 41 - The tracepoint statement, in C code.
64 In subsys/file.c (where the tracing statement must be added)::
123 within an if statement with the following::
142 the static_key of the tracepoint to allow the if statement to be implemented
|
| /linux-5.10/Documentation/translations/zh_CN/process/ |
| D | index.rst | 34 kernel-enforcement-statement
35 kernel-driver-statement
|
| /linux-5.10/Documentation/translations/it_IT/process/ |
| D | index.rst | 34 kernel-enforcement-statement
35 kernel-driver-statement
|
| /linux-5.10/scripts/kconfig/ |
| D | parser.y | 104 fprintf(stderr, "%s:%d: missing end statement for this entry\n",
130 | stmt_list T_WORD error T_EOL { zconf_error("unknown statement \"%s\"", $2); }
131 | stmt_list error T_EOL { zconf_error("invalid statement"); }
139 | stmt_list_in_choice error T_EOL { zconf_error("invalid statement"); }
168 zconfprint("warning: menuconfig statement without prompt");
429 /* prompt statement */
470 /* assignment statement */
|
| /linux-5.10/tools/testing/selftests/ |
| D | kselftest_harness.h | 116 * SKIP(statement, fmt, ...)
118 * @statement: statement to run after reporting SKIP
123 * and runs "statement", which is usually "return" or "goto skip".
125 #define SKIP(statement, fmt, ...) do { \ argument
135 statement; \
151 * as such. Returning early may be performed with a bare "return;" statement.
170 * as such. Returning early may be performed with a bare "return;" statement.
258 * A bare "return;" statement may be used to return early.
281 * A bare "return;" statement may be used to return early.
|
| /linux-5.10/Documentation/core-api/ |
| D | symbol-namespaces.rst | 79 unit as preprocessor statement. The above example would then read::
95 using a statement like::
109 It is advisable to add the MODULE_IMPORT_NS() statement close to other module
|
| /linux-5.10/drivers/s390/char/ |
| D | vmur.h | 21 * both in SPOOL directory control statement and in CP DEFINE statement
|
| /linux-5.10/arch/arm64/include/asm/ |
| D | kgdb.h | 44 * protocol for AArch64 was developed it depended on a statement in the
47 * protocol. In fact this statement is still present in ARM DDI 0487A.i.
|
| /linux-5.10/include/asm-generic/ |
| D | bug.h | 236 * a stand alone line statement or as a condition in an if ()
237 * statement.
238 * A simple "0" would cause gcc to give a "statement has no effect"
|
1234567891011