update for V2024.05 release #43
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tnmysh
approved these changes
May 30, 2024
|
@arnopo This needs to be split into two. The update to Zephyr 3.6 should be done in main and the lock to v2024.05 should be done in the v2024.05 branch. I will cherry pick these to do this. |
Update to the last openamp and libmetal versions Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
|
@wmamills |
|
I am waiting to create the v2024.05 branch until I have tested and landed any new commits. Last time I created the branch early and had to duplicate commits to both branches. I would prefer to minimize that. |
|
@arnopo please re-target this PR to the v2024.05 branch and then go ahead and merge it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update the zephyr version and point to the v2024.05 release candidate