Lines Matching refs:functions

35 benefit of warning you when you're nesting your functions too deep.
116 However, there is one special case, namely functions: they have the
126 (a) K&R are _right_ and (b) K&R are right.  Besides, functions are
183 somewhat like functions (and are usually used with parentheses in Linux,
253 have descriptive names, as do global functions.  If you have a function
294      the proper accessor functions.
296      NOTE! Opaqueness and "accessor functions" are not good in themselves.
362 maximum limits all the more closely.  Use helper functions with
374 In source files, separate functions with one blank line.  If the function is
389 		Chapter 7: Centralized exiting of functions
460 When commenting the kernel API functions, please use the kernel-doc format.
622 CAPITALIZED macro names are appreciated but macros resembling functions
625 Generally, inline functions are preferable to macros resembling functions.
666 functions:
703 messages.  While the other pr_XXX() functions print unconditionally,
759 A reasonable rule of thumb is to not put inline at functions that have more
766 Often people argue that adding inline to functions that are static and used
797 All EXPORTed functions must respect this convention, and so should all
798 public functions.  Private (static) functions need not, but it is
804 result.  Typical examples would be functions that return pointers; they use
860 Consider writing simple helper functions that wrap common bits of inline
864 Large, non-trivial assembly functions should go in .S files, with corresponding
866 functions should use "asmlinkage".
886 use such conditionals in a header file defining functions for use in those .c
888 functions unconditionally from .c files.  The compiler will avoid generating
892 Prefer to compile out entire functions, rather than portions of functions or