Lines Matching refs:description

64    * function_name() - Brief description of function.
70    * A longer description, with more discussion of the function function_name()
75    * The longer description may have multiple paragraphs.
82    * The return value description can also have multiple paragraphs, and should
86 The brief description following the function name may span multiple lines, and
87 ends with an argument description, a blank comment line, or the end of the
94 the short function description.  Do not leave a blank line between the
95 function description and the arguments, nor between the arguments.
97 Each ``@argument:`` description may span multiple lines.
101    If the ``@argument`` description has multiple lines, the continuation
102    of the description should start at the same column as the previous line::
104       * @argument: some long description
110       *		some long description
113 If a function has a variable number of arguments, its description should
116       * @...: description
174    * struct struct_name - Brief description.
187 The brief description following the structure name may span multiple
188 lines, and ends with a member description, a blank comment line, or the
195 as function parameters; they immediately succeed the short description
198 Inside a struct or union description, you can use the ``private:`` and
209    * struct my_struct - short description
214    * Longer description
285    * struct foo - Brief description.
297          * Here, the member description may contain several paragraphs.
301                 /** @foobar: Single line description. */
319    * typedef type_name - Brief description.
327    * typedef type_name - Brief description.
328    * @arg1: description of arg1
329    * @arg2: description of arg2
365   a function description.