Skip to content

STM32F429ZI add SERIAL_ASYNCH #6088

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
Feb 16, 2018
Merged

STM32F429ZI add SERIAL_ASYNCH #6088

merged 1 commit into from
Feb 16, 2018

Conversation

pilotak
Copy link
Contributor

@pilotak pilotak commented Feb 13, 2018

Related to #6080

@mbed-ci
Copy link

mbed-ci commented Feb 13, 2018

--none--

@0xc0170
Copy link
Contributor

0xc0170 commented Feb 14, 2018

@pilotak did you run any tests for this change?

@ohagendorf
Copy link
Contributor

Exactly the same MCU in another target (DISCO_F429ZI) had the SERIAL_ASYNCH flag already set.

@pilotak
Copy link
Contributor Author

pilotak commented Feb 15, 2018

compiles fine, i don't know what other tests you need

@0xc0170
Copy link
Contributor

0xc0170 commented Feb 15, 2018

/morph build

@mbed-ci
Copy link

mbed-ci commented Feb 15, 2018

Build : SUCCESS

Build number : 1146
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/6088/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

@mbed-ci
Copy link

mbed-ci commented Feb 15, 2018

@mbed-ci
Copy link

mbed-ci commented Feb 15, 2018

@cmonr
Copy link
Contributor

cmonr commented Feb 16, 2018

@pilotak For future reference, the test results that we're looking for come from the command mbed test

I also ran a local instance with this PR against GCC, and results were good.

@cmonr cmonr merged commit 659bcc3 into ARMmbed:master Feb 16, 2018
@pilotak
Copy link
Contributor Author

pilotak commented Feb 17, 2018

@cmonr Ok that's fine will test it next time

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

Successfully merging this pull request may close these issues.

6 participants