west.yml: segger: RTT control block init mode Kconfigs #81425
Conversation
|
The following west manifest projects have changed revision in this Pull Request:
✅ All manifest checks OK Note: This message is automatically posted and updated by the Manifest GitHub Action. |
zephyrbot
added
manifest
manifest-segger
DNM
brycewilkins
force-pushed
the
bw/update_west_segger
branch
from
eefa07a to
17dc2cb
Compare
|
@nordicjm @carlescufi The PR #53569 is in v4.0.0 so it would be great to have the Segger PR (zephyrproject-rtos/segger#17) merged and the west.yml updated so this can all work together. Fingers crossed... |
|
Too late for 4.0, the release is today, but it can be merged to main after the release is finished and the 2 day review period has passed, and be in (early) for 4.1 |
|
Converted to draft; zephyrproject-rtos/segger#17 needs to be rebased to fix the build errors. Update: rebased and now passing tests. |
brycewilkins
force-pushed
the
bw/update_west_segger
branch
from
17dc2cb to
37a4558
Compare
|
@brycewilkins - the module pr has been merged. Please update this PR to include the correct commit in west.yml |
Kconfig options for RTT control block initialization and linker section were added in zephyrproject-rtos#53569, however the Zephyr west.yml was not updated to incorporate the Segger repository changes to make use of the new Kconfig options. This fixes that. Signed-off-by: Bryce Wilkins <[email protected]>
brycewilkins
force-pushed
the
bw/update_west_segger
branch
from
37a4558 to
638d26b
Compare
6 participants
Kconfig options for RTT control block initialization and linker section were added in #53569, however the Zephyr west.yml was not updated to incorporate the Segger repository changes (zephyrproject-rtos/segger#17) required to make use of the new Kconfig options.
This fixes that by updating west.yml.
Segger repository changes by @giansta