Lines Matching full:use
72 Don't use commas to avoid using braces:
197 Do not unnecessarily use braces where a single statement will do.
214 statement; in the latter case use braces in both branches:
225 Also, use braces when a loop contains more than a single simple statement:
237 Linux kernel style for use of spaces depends (mostly) on
238 function-versus-keyword usage. Use a space after (most) keywords. The
244 So use a space after these keywords::
264 preferred use of ``*`` is adjacent to the data name or function name and not
274 Use one space around (on each side of) most binary and ternary operators,
310 Unlike Modula-2 and Pascal programmers, C programmers do not use cute
362 Please don't use things like ``vps_t``.
363 It's a **mistake** to use typedef for structures and pointers. When you see a
409 ``unsigned long``, then by all means go ahead and use a typedef.
411 (c) when you use sparse to literally create a **new** type for
419 some people object to their use anyway.
429 (e) Types safe for use in userspace.
432 require C99 types and cannot use the ``u32`` form above. Thus, we
433 use __u32 and similar types in all structures which are shared
437 EVER use a typedef unless you can clearly match one of those rules.
459 maximum limits all the more closely. Use helper functions with
490 Do not use the ``extern`` keyword with function declarations as this makes
615 When commenting the kernel API functions, please use the kernel-doc format.
626 * Please use it consistently.
633 types. To this end, use just one data declaration per line (no commas for
635 item, explaining its use.
648 So, you can either get rid of GNU emacs, or change it to use saner
704 everything is lost: use ``indent``.
711 options ``-kr -i8`` (stands for ``K&R, 8 character indents``), or use
718 Note that you can also use the ``clang-format`` tool to help you with
900 of kernel messages to make a good impression. Do not use incorrect
901 contractions like ``dont``; use ``do not`` or ``don't`` instead. Make the
909 which you should use to make sure messages are matched to the right device
914 so prefer to use dev_dbg/pr_debug unless something is wrong.
971 without __GFP_NOWARN so there is no use in emitting an additional failure
978 faster" speedup option called ``inline``. While the use of inlines can be
980 very often is not. Abundant use of the inline keyword leads to a much bigger
1033 result. Typical examples would be functions that return pointers; they use
1048 bool function return types and stack variables are always fine to use whenever
1049 appropriate. Use of bool is encouraged to improve readability and is often a
1052 Do not use bool if cache line layout or size of the value matters, as its size
1054 optimized for alignment and size should not use bool.
1064 Otherwise limited use of bool in structures and arguments can improve
1071 you should use, rather than explicitly coding some variant of them yourself.
1079 Similarly, if you need to calculate the size of some structure member, use
1119 includes markers for indentation and mode configuration. People may use their
1127 In architecture-specific code, you may need to use inline assembly to interface
1129 However, don't use inline assembly gratuitously when C can do the job. You can
1134 that inline assembly can use C parameters.
1138 functions should use ``asmlinkage``.
1159 Wherever possible, don't use preprocessor conditionals (#if, #ifdef) in .c
1161 use such conditionals in a header file defining functions for use in those .c
1178 Within code, where possible, use the IS_ENABLED macro to convert a Kconfig
1179 symbol into a C boolean expression, and use it in a normal C conditional:
1191 references, etc). Thus, you still have to use an #ifdef if the code inside the
1218 Use WARN() rather than BUG()
1222 BUG_ON(), or VM_BUG_ON(). Instead, use a WARN*() variant, preferably
1227 internal corruptions with no way of continuing may still use BUG(), but need
1230 Use WARN_ON_ONCE() rather than WARN() or WARN_ON()
1255 panic_on_warn users is not a valid reason to avoid the judicious use
1261 Use BUILD_BUG_ON() for compile-time assertions
1264 The use of BUILD_BUG_ON() is acceptable and encouraged, because it is a