[Backport v3.0-branch] NCSDK-32650: Revert incompatible memory changes #2737
Conversation
This file contains hidden or 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
tomchy
changed the title
tomchy
changed the title
nordic-segl
approved these changes
Apr 9, 2025
|
FYI - compliance fails (as if PR in the upstream was merged in mean time. Thus, this PR is no longer [from list] -> [from tree]) |
…lue." This reverts commit 1e69738. Ref: NCSDK-32650 Signed-off-by: Tomasz Chyrowicz <[email protected]> This reverts commit 1e69738 (cherry picked from commit 062e6e1)
This reverts commit a53cb73. Ref: NCSDK-32650 Signed-off-by: Tomasz Chyrowicz <[email protected]> This reverts commit a53cb73. (cherry picked from commit db34319)
tomchy
force-pushed
the
backport-21408-to-v3.0-branch
branch
from
330af46 to
8d9815e
Compare
|
bjarki-andreasen
merged commit 7e1daf0
into
nrfconnect:v4.0.99-ncs1-branch
18 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Due to compatibility reasons, we should either revert those or provide a clear and tested way to migrate between the v2.9.0-nRF54H20-1 and v3.0.0.