Lines Matching refs:function

49 Kernel-doc comments should be placed just before the function
52 Example kernel-doc function comment:
55  * foobar() - short function description of foobar
61  * A longer description, with more discussion of the function foobar()
76 this opening short function description line, with no intervening
79 If a function parameter is "..." (varargs), it should be listed in
97 The kernel-doc function comments describe each parameter to the
98 function, in order, with the @name lines.
199 If you just want to view the documentation for one function in one
202 $ scripts/kernel-doc -man -function fn file | nroff -man | less
206 $ scripts/kernel-doc -text -function fn file
218  * (Description:)? (Description of function)?
227 "section header:" names must be unique per function (or struct,
231 of a function.
233 Avoid putting a spurious blank line after the function name, or else the
239 'funcname()' - function
277 enums and typedefs. Instead of the function name you must write the name
340 functions that are exported using EXPORT_SYMBOL: the function list is
349 !F<filename> <function [functions...]> is replaced by the