Searched refs:conventions (Results 1 – 20 of 20) sorted by relevance
7 * Follow the Devicetree specification conventions and rules.
51 See sections below for more information about how to build and run them, as well as the conventions140 …mple test <tests/bsim/bluetooth/host/misc/sample_test/README.rst>` for conventions that apply to t…161 Please follow the existing conventions and do not design one-off bespoke runners (e.g. a python176 Here are the conventions:
81 `discovery rules <https://docs.pytest.org/en/7.1.x/explanation/goodpractices.html#conventions-for-p…
130 …es/Specification/HTML/Core-60/out/en/architecture,-change-history,-and-conventions/architecture.ht…131 …es/Specification/HTML/Core-60/out/en/architecture,-change-history,-and-conventions/architecture.ht…
149 <https://arm-software.github.io/psa-api/crypto/1.2/overview/conventions.html#concurrent-calls>`_154 …`Stability of parameters <https://arm-software.github.io/psa-api/crypto/1.2/overview/conventions.h…
23 - The introduction of new idiomatic usage or conventions, even if they do not
53 partitioning conventions used for :ref:`dfu` via the MCUboot bootloader, as
97 following conventions. Every supported C standard library shall:
286 conventions.292 point instructions are generated but soft-float calling conventions.
72 as they match existing conventions. This discussion will be limited
95 Naming conventions
388 These macros have tricky naming conventions which the :ref:`devicetree_api` API
91 Similar conventions exist for representing other types of hardware.
199 The calls obey standard calling conventions; i.e., the state
176 conventions. Functional correctness is ensured by the build system and366 the code review. These coding conventions are enforced by
121 Other options for timeout initialization follow the unit conventions
425 associated pin control configuration is based on variable naming conventions.
306 conventions and documentation of deviations.
564 conventions are as follows:
917 has also been adjusted to follow common conventions. Below you can find the1546 * :github:`36811` - Clarify ``Z_`` APIs naming conventions and intended scope
