Skip to content

STM32: Align HAL & US tickers #4809

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
Aug 14, 2017

Conversation

betzw
Copy link
Contributor

@betzw betzw commented Jul 25, 2017

See PR #4768!

@0xc0170
Copy link
Contributor

0xc0170 commented Jul 26, 2017

@0xc0170 0xc0170 changed the title Align HAL & US tickers STM32: Align HAL & US tickers Jul 31, 2017
@0xc0170
Copy link
Contributor

0xc0170 commented Aug 6, 2017

/morph test

1 similar comment
@0xc0170
Copy link
Contributor

0xc0170 commented Aug 7, 2017

/morph test

@mbed-bot
Copy link

mbed-bot commented Aug 7, 2017

Result: FAILURE

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

/morph test

Output

mbed Build Number: 956

Build failed!

@0xc0170
Copy link
Contributor

0xc0170 commented Aug 9, 2017

/morph test

@mbed-bot
Copy link

mbed-bot commented Aug 9, 2017

Result: FAILURE

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

/morph test

Output

mbed Build Number: 975

Example Build failed!

@0xc0170
Copy link
Contributor

0xc0170 commented Aug 9, 2017

/morph test

@mbed-bot
Copy link

Result: FAILURE

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

/morph test

Output

mbed Build Number: 985

Example Build failed!

@0xc0170
Copy link
Contributor

0xc0170 commented Aug 10, 2017

/morph test

1 similar comment
@theotherjimmy
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: 995

All builds and test passed!

@adbridge
Copy link
Contributor

This relies on #4644 which is marked for 5.6.0 , thus re-targeting this PR also.

@LMESTM
Copy link
Contributor

LMESTM commented Sep 4, 2017

@adbridge #4644 has introduced a regression which is being fixed in #5012 so please consider #5012 as well in 5.6

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