Home
last modified time | relevance | path

Searched refs:propagate (Results 1 – 11 of 11) sorted by relevance

/Zephyr-latest/share/sysbuild/cmake/modules/
Dsysbuild_root.cmake45 # have been added to the cache in order for the settings to propagate to images.
Dsysbuild_kconfig.cmake26 # to the cache in order for the setting to propagate to images.
/Zephyr-latest/cmake/modules/
DFindTargetTools.cmake67 # Zephyr Kconfig defines BIG_ENDIAN according to arch, SoC, Board, so propagate
/Zephyr-latest/doc/connectivity/networking/api/
Dcapture.rst92 The packets propagate to interface 2 because it is linked to the first interface.
/Zephyr-latest/doc/kernel/usermode/
Dsyscalls.rst562 failures should propagate a return value to the caller, and which should
584 invoking :c:func:`z_thread_malloc()`, should propagate ``-ENOMEM`` to the
603 checked in the verification function and propagate a return value to the
621 when bad parameters are passed in as they do not propagate errors.
/Zephyr-latest/doc/hardware/cache/
Dguide.rst146 caching in which data writes from the processor core propagate through to
/Zephyr-latest/scripts/
Dspelling.txt1252 propigate||propagate
1255 propogate||propagate
/Zephyr-latest/
DCMakeLists.txt1813 $<$<BOOL:${CONFIG_BUILD_OUTPUT_META_STATE_PROPAGATE}>:--meta-state-propagate>
/Zephyr-latest/doc/releases/
Drelease-notes-2.3.rst1035 * :github:`24178` - CI: extra_args from sanitycheck ``*.yaml`` do not propagate to cmake
Drelease-notes-2.4.rst1129 * :github:`27597` - build system fails to propagate devicetree change to Kconfig
Drelease-notes-3.3.rst3041 * :github:`53579` - add_compile_definitions does not "propagate upwards" as supposed to when using …