psa: Be compatible with deprecated constants #65
No reviewers
Labels
No labels
api-spec
bug
CLA requested
CLA valid
compliance
DO NOT MERGE
duplicate
enhancement
feature branch
good first issue
HEADER FORMATTING ISSUE
help wanted
Information
invalid
Jira status: AWAITING REVIEW
Jira status: CLOSED
Jira status: DONE
Jira status: IN PROGRESS
Jira status: IN REVIEW
Jira status: OPEN
Jira status: REOPENED
Jira status: RESOLVED
mirrored
mirror internally
needs: backports
needs: ci
needs: design review
needs: preceding PR
needs: review
needs: work
notabug
open for community contribution
Product Backlog
question
ready for merge
security
stale
type: bug
type: enhancement
type: question
web pages
wontfix
writing
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-ARMmbed/mbed-crypto!65
Loading…
Reference in a new issue
No description provided.
Delete branch "deprecated-constants-compat"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In case the new constants aren't available yet in Mbed TLS, continue to
use the deprecated constants if they are available.
This breaks a cyclic dependency between Mbed Crypto needing new constants from Mbed TLS as well as Mbed TLS needing new PSA Crypto before either can ship into Mbed OS.
Only CI failure on Jenkins CI is FreeBSD Timing test, a known-flaky test.
Jenkins CI is passing, which is more thorough than the Travis CI.