manifest: tf-m: include fix for Mbed TLS cipher interface #99161
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. |
github-actions
bot
added
manifest
manifest-trusted-firmware-m
DNM (manifest)
zephyrbot
added
size: XS
|
FYI @jhedberg @cfriedt this is a fixup to #98786, IMO a showstopper so would be good to get into 4.3.0, it's low risk as it's just aligning some duplicated files between Mbed TLS and TF-M (the latter unfortunately keeps copies of files of the former, and they fell out of sync with the update of Mbed TLS) |
valeriosetti
force-pushed
the
tfm-fix-cipher-interface
branch
2 times, most recently
from
7518a1c to
905f85c
Compare
Update manifest to align the copy of Mbed TLS header files which lives in the TF-M repository to what's in Mbed TLS release v3.6.5. Signed-off-by: Valerio Setti <[email protected]>
valeriosetti
dismissed stale reviews from tomi-font, Vge0rge, and jhedberg
via
9aa6e46
valeriosetti
force-pushed
the
tfm-fix-cipher-interface
branch
from
905f85c to
9aa6e46
Compare
github-actions
bot
removed
the
DNM (manifest)
|
|
@tomi-font do you mind being added as a co-maintainer of tf-m related areas? Looks like we need more coverage here and many of those PRs related to TF-M keep getting stuck |
Sure, as long as expectations are not too high I'm happy to help out. At least should help with moving things forward as @d3zd3z has mostly been irresponsive. |
Upgrade from collaborator to maintainer as suggested in zephyrproject-rtos#99161 (comment). Signed-off-by: Tomi Fontanilles <[email protected]>
Upgrade from collaborator to maintainer as suggested in zephyrproject-rtos#99161 (comment). Signed-off-by: Tomi Fontanilles <[email protected]>
9 participants
Update manifest to include a fix in Mbed TLS interface header files for cipher module.
Resolves #99153