Lines Matching refs:use

11 Many of the rules given below (such as indentation size, use of tabs, and
48 the remote master, use:
76 Avoid printf and use logging macros
155 used (Banned) or are discouraged from use and must be used with care (Caution).
160 | ``strcpy, wcscpy``,    | Banned    | use strlcpy instead                  |
163 | ``strcat, wcscat``,    | Banned    | use strlcat instead                  |
166 | ``sprintf, vsprintf``  | Banned    | use snprintf, vsnprintf              |
175 | ``strtok``             | Banned    | use strtok_r or strsep instead       |
179 | ``ato*``               | Banned    | use equivalent strto* functions      |
192 Where possible, use the ``CASSERT`` macro to check the validity of data known at
351 - Where possible, use the built-in *C* data types for variable storage (for
369 - Avoid use of ``short`` as this may end up being slower than ``int`` in some
370   systems. If a variable must be exactly 16-bit, use ``int16_t`` or
373 - Avoid use of ``long``. This is guaranteed to be at least 32-bit but, given
374   that `int` is 32-bit on Arm platforms, there is no use for it. For integers of
375   at least 64-bit, use ``long long``.
389     simply use a pointer to that type (for example: ``struct my_struct *``).
393     structure that is likely to require pointer arithmetic then use
398   - For other pointer arguments in a function declaration, use ``void *``. This
424   example, the following struct in ``ep_info.h`` could use this type to minimize
463 debug symbols must manually be included. Please use the ``func_prologue`` and
464 ``func_epilogue`` macros if you need to use the stack. Also, obeying the
467 Do not use weak functions
476 The use of weak functions is highly discouraged in the TF-A codebase. Newly
502 reason, the TF-A project used to make heavy use of weak functions and there