Home
last modified time | relevance | path

Searched refs:rerun (Results 1 – 8 of 8) sorted by relevance

/Zephyr-latest/subsys/ipc/ipc_service/lib/
Dicmsg.c158 bool rerun = false; in callback_process() local
189 rerun = true; in callback_process()
241 rerun = true; in callback_process()
317 rerun = (data_available(dev_data) > 0); in callback_process()
331 return rerun; in callback_process()
337 bool rerun; in workq_callback_process() local
340 rerun = callback_process(dev_data); in workq_callback_process()
341 if (rerun) { in workq_callback_process()
350 bool rerun; in mbox_callback() local
354 ARG_UNUSED(rerun); in mbox_callback()
[all …]
/Zephyr-latest/doc/develop/toolchains/
Dzephyr_sdk.rst131 You must rerun the setup script if you relocate the Zephyr SDK bundle directory after
187 You must rerun the setup script if you relocate the Zephyr SDK bundle directory after
229 You must rerun the setup script if you relocate the Zephyr SDK bundle directory after
/Zephyr-latest/boards/native/nrf_bsim/doc/
Dnrf52_bsim.rst96 initialization script (``~/.bashrc``), so you won't need to rerun them
/Zephyr-latest/doc/develop/test/
Dpytest.rst296 How to rerun locally pytest tests without rebuilding application by Twister?
/Zephyr-latest/doc/services/logging/
Dcs_stm.rst151 If the log capture fails to find a sync, rerun the capture process.
/Zephyr-latest/share/sysbuild/cmake/modules/
Dsysbuild_extensions.cmake119 # CMAKE_RERUN : Force a CMake rerun for the application during next build
/Zephyr-latest/doc/contribute/
Dguidelines.rst586 If a test fails, you can check from the CI run logs how to rerun it locally,
/Zephyr-latest/cmake/modules/
Dextensions.cmake3273 # invocation triggering a CMake rerun doesn't rely on the