Searched refs:patches (Results 26 – 33 of 33) sorted by relevance
12
| /Zephyr-latest/boards/openisa/rv32m1_vega/doc/ |
| D | index.rst | 716 - Base toolchain: `pulp-riscv-gnu-toolchain`_; extra toolchain patches:
757 some additional patches hosted in a separate repository,
760 `readme.md`_ file to apply the patches, then run::
|
| /Zephyr-latest/doc/project/ |
| D | dev_env_and_tools.rst | 14 patches, which are then reviewed by the project members before being applied to
209 Developers are expected to fix issues and rework their patches and submit again.
|
| D | release_process.rst | 58 of patches for each release. At the beginning of each development cycle, the
395 - Has a dedicated maintainer who commits to respond to issues / review patches.
|
| /Zephyr-latest/boards/espressif/esp32s3_eye/doc/ |
| D | index.rst | 252 ESP32-S3 modules require patches to OpenOCD that are not upstreamed yet.
|
| /Zephyr-latest/doc/contribute/ |
| D | guidelines.rst | 7 patches directly to the project. In our collaborative open source environment,
12 and enhancement requests, and submit patches to the project so your patch will
169 for the Project to use. Developers are permitted to cherry-pick patches that
173 * the content of the patches will not be substantially modified,
|
| /Zephyr-latest/doc/develop/languages/cpp/ |
| D | index.rst | 254 https://gcc.gnu.org/pipermail/gcc-patches/2017-November/487584.html
|
| /Zephyr-latest/boards/espressif/esp32_ethernet_kit/doc/ |
| D | index.rst | 548 As with much custom hardware, the ESP32 modules require patches to
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-3.3.rst | 705 STM32 DMA, Intel HDA, and Intel GPDMA all comply with the contract after patches.
|
12
