Lines Matching refs:use

156 Do not unnecessarily use braces where a single statement will do.
169 statement; in the latter case use braces in both branches:
180 Linux kernel style for use of spaces depends (mostly) on
187 So use a space after these keywords:
201 preferred use of '*' is adjacent to the data name or function name and not
243 and Pascal programmers, C programmers do not use cute names like
275 Please don't use things like "vps_t".
276 It's a _mistake_ to use typedef for structures and pointers. When you see a
313      "unsigned long", then by all means go ahead and use a typedef.
315  (c) when you use sparse to literally create a _new_ type for
323      some people object to their use anyway.
333  (e) Types safe for use in userspace.
336      require C99 types and cannot use the 'u32' form above. Thus, we
337      use __u32 and similar types in all structures which are shared
341 EVER use a typedef unless you can clearly match one of those rules.
460 When commenting the kernel API functions, please use the kernel-doc format.
465 Don't use C99-style "// ..." comments.
472 	 * Please use it consistently.
489 types.  To this end, use just one data declaration per line (no commas for
491 item, explaining its use.
503 So, you can either get rid of GNU emacs, or change it to use saner
540 everything is lost: use "indent".
547 options "-kr -i8" (stands for "K&R, 8 character indents"), or use
685 of kernel messages to make a good impression. Do not use crippled
686 words like "dont"; use "do not" or "don't" instead.  Make the messages
694 which you should use to make sure messages are matched to the right device
750 faster" speedup option called "inline". While the use of inlines can be
752 very often is not. Abundant use of the inline keyword leads to a much bigger
804 result.  Typical examples would be functions that return pointers; they use
811 you should use, rather than explicitly coding some variant of them yourself.
817 Similarly, if you need to calculate the size of some structure member, use
848 includes markers for indentation and mode configuration.  People may use their
855 In architecture-specific code, you may need to use inline assembly to interface
857 However, don't use inline assembly gratuitously when C can do the job.  You can
862 that inline assembly can use C parameters.
866 functions should use "asmlinkage".
884 Wherever possible, don't use preprocessor conditionals (#if, #ifdef) in .c
886 use such conditionals in a header file defining functions for use in those .c
903 Within code, where possible, use the IS_ENABLED macro to convert a Kconfig
904 symbol into a C boolean expression, and use it in a normal C conditional:
914 references, etc).  Thus, you still have to use an #ifdef if the code inside the