Skip to content

Update mbed TLS to version 2.3.0 #2235

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 25, 2016
Merged

Update mbed TLS to version 2.3.0 #2235

merged 1 commit into from
Jul 25, 2016

Conversation

sg-
Copy link
Contributor

@sg- sg- commented Jul 23, 2016

This PR imports mbed TLS into mbed. It updates the mbed TLS library to the standalone release 2.3.0

@sg-
Copy link
Contributor Author

sg- commented Jul 23, 2016

@mbed-bot: TEST

HOST_OSES=windows
BUILD_TOOLCHAINS=GCC_ARM,ARM,IAR
TARGETS=K64F,NRF51_DK,NRF51_MICROBIT,NUCLEO_F411RE

@sg-
Copy link
Contributor Author

sg- commented Jul 23, 2016

/morph test

@mbed-bot
Copy link

[Build 689]
SUCCESS: Building succeeded and tests were run! Be sure to check the test results

@mbed-bot
Copy link

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 491

A build failure occurred!

@bridadan
Copy link
Contributor

/morph test

@mbed-bot
Copy link

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 499

Test failed!

@simonbutcher
Copy link
Contributor

simonbutcher commented Jul 25, 2016

Hi @sg-

Reviewing the PR. Small issues - but the importer script references the wrong repo (line 38, features/mbedtls/importer/Makefile) and features/mbedtls/importer/TARGET_IGNORE/.gitignore references an obsolete repo.

I am guessing both of those issues are copied from the source.

The PR is otherwise ok, and I suggest you merge with this PR and we can fix these wrinkles with a secondary PR.

@sg- sg- merged commit fb7c9f8 into ARMmbed:master Jul 25, 2016
@sg-
Copy link
Contributor Author

sg- commented Jul 25, 2016

@sbutcher-arm thanks! Was gonna update to the proper repo but I don't know which they are. Please update when you have a chance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants