Home
last modified time | relevance | path

Searched full:strategy (Results 1 – 17 of 17) sorted by relevance

/Zephyr-Core-2.7.6/.github/workflows/
Dtwister.yaml117 strategy:
200 …./scripts/twister --subset ${{matrix.subset}}/${{ strategy.job-total }} ${TWISTER_COMMON} ${PUSH_O…
209 …./scripts/twister --subset ${{matrix.subset}}/${{ strategy.job-total }} --load-tests testplan.csv …
216 …./scripts/twister --subset ${{matrix.subset}}/${{ strategy.job-total }} ${TWISTER_COMMON} ${DAILY_…
Dtwister_tests.yml28 strategy:
Dfootprint-tracking.yml27 strategy:
Dfootprint.yml16 strategy:
Ddevicetree_checks.yml25 strategy:
Dwest_cmds.yml26 strategy:
Dclang.yaml17 strategy:
Dcodecov.yaml19 strategy:
/Zephyr-Core-2.7.6/doc/development_process/
Dproposals.rst121 communicates the high-level overview of a project's strategy, while a release
149 The release plan comes into play when the project roadmap's high-level strategy
/Zephyr-Core-2.7.6/doc/guides/west/
Dtroubleshooting.rst32 One strategy is to go to ``/some/directory``, copy/paste and run the entire
/Zephyr-Core-2.7.6/boards/xtensa/intel_adsp_cavs25/doc/
Dindex.rst53 plan on a strategy that can tolerate data loss on the device you're
/Zephyr-Core-2.7.6/kernel/
Duserspace.c41 /* The originally synchronization strategy made heavy use of recursive
/Zephyr-Core-2.7.6/drivers/interrupt_controller/
Dintc_esp32.c786 * Interrupt disabling strategy:
/Zephyr-Core-2.7.6/doc/contribute/
Dindex.rst651 * Test Strategy
/Zephyr-Core-2.7.6/doc/security/
Dsecurity-overview.rst477 security strategy and architecture, and the preparation of audits
/Zephyr-Core-2.7.6/doc/releases/
Drelease-notes-2.0.rst746 …b:`17962` - BLE Mesh Recommended memory allocation due to who is assigned who releases the strategy
Drelease-notes-2.6.rst1985 * :github:`32075` - net: lwm2m: Testing Strategy for LWM2M Engine