Searched refs:criteria (Results 1 – 23 of 23) sorted by relevance
| /Zephyr-latest/subsys/bluetooth/mesh/ |
| D | transport.h | 44 uint8_t criteria; member
|
| D | friend.c | 1014 if (!MIN_QUEUE_SIZE_LOG(msg->criteria)) { in bt_mesh_friend_req()
1019 if (CONFIG_BT_MESH_FRIEND_QUEUE_SIZE < MIN_QUEUE_SIZE(msg->criteria)) { in bt_mesh_friend_req()
1021 CONFIG_BT_MESH_FRIEND_QUEUE_SIZE, MIN_QUEUE_SIZE(msg->criteria)); in bt_mesh_friend_req()
1068 delay = offer_delay(frnd, rx->ctx.recv_rssi, msg->criteria); in bt_mesh_friend_req()
|
| D | lpn.c | 373 .criteria = LPN_CRITERIA, in send_friend_req()
|
| /Zephyr-latest/boards/ |
| D | index.rst | 22 * A board must meet **all** criteria selected across different fields. For example, if you select
|
| /Zephyr-latest/ |
| D | CONTRIBUTING.rst | 21 ensure developers are following licensing criteria for their
|
| /Zephyr-latest/doc/project/ |
| D | release_process.rst | 90 considered to be sufficiently stable and the release criteria have been achieved
100 The main motivation is to clearly have the criteria in place that must be met
105 - The release criteria documents all the requirements of our target audience for
108 - The criteria at any given time are not set in stone: there may be requirements
109 that have been overlooked, or that are new, and in these cases, the criteria
112 Below is the high level criteria to be met for each release:
482 When all final release criteria has been met and the final release notes
|
| D | code_flow.rst | 44 * Define exit criteria for merging the collaboration branch changes back into the main branch.
|
| D | project_roles.rst | 107 approvals needed to merge a PR. Other criteria for merging may apply.
141 required approvals needed to merge a PR. Other criteria for merging may apply.
222 maintainers and follow the merge criteria of a change.
362 approvals, the merge criteria is extended with the guidelines below:
|
| D | dev_env_and_tools.rst | 172 dismissed following the criteria below:
|
| /Zephyr-latest/doc/build/ |
| D | zephyr_cmake_package.rst | 100 the following criteria will be used:
186 criteria.
|
| /Zephyr-latest/doc/security/ |
| D | security-overview.rst | 241 The development of secure code shall adhere to certain criteria. These
361 The quality assurance part encompasses the following criteria:
480 These criteria and tasks need to be integrated into the development
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | kernelobjects.rst | 106 the object placement criteria will have their memory addresses placed in a
|
| /Zephyr-latest/doc/contribute/ |
| D | external.rst | 173 detail, so that you are informed of the criteria used by the TSC and board in
|
| D | bin_blobs.rst | 244 detail, so that you are informed of the criteria used by the TSC in order to
|
| D | guidelines.rst | 91 To make a good faith effort to ensure licensing criteria are met, the Zephyr
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | mcp.rst | 63 according to various criteria, with the result returned in the *search
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | main.rst | 40 Each available iface is considered ready if it meets the following criteria:
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | mailboxes.rst | 435 certain criteria, thereby eliminating unneeded data copying. The message
|
| /Zephyr-latest/doc/develop/test/ |
| D | ztest.rst | 451 interrupt handler context). Completion criteria is set to at least 10000 executions
|
| D | twister.rst | 516 Twister to be able to evaluate if a test passes criteria. For example, a
|
| /Zephyr-latest/doc/contribute/documentation/ |
| D | guidelines.rst | 1227 quickly browse the list of all supported boards and filter them according to various criteria.
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-4.0.rst | 414 * Added a new :ref:`interactive board catalog <boards>` enabling users to search boards by criteria
|
| D | release-notes-3.1.rst | 614 * Changed :c:struct:`coap_pending` allocation criteria. This now uses a data
|
