Test merge of development and TLS PR 2028 #73
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!73
Loading…
Reference in a new issue
No description provided.
Delete branch "dev/Patater/dev-2028-merge"
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?
For testing:
Merge the current Mbed TLS development branch.
Merge https://github.com/ARMmbed/mbedtls/pull/2028
If testing goes well, we'll push this already reviewed and tested code from Mbed TLS into Mbed Crypto
development, as Mbed TLS requires the new functionmbedtls_asn1_write_named_bitstring()present in the crypto submodule in order to pass their tests and be able to merge https://github.com/ARMmbed/mbedtls/pull/2028 into Mbed TLSdevelopment.Testing went well. Manually pushed to development branch. Code landing was already reviewed by TLS team (coming from the TLS development branch) and additionally in https://github.com/ARMmbed/mbedtls/pull/2028 (for the code from there)