Skip to content

InterruptIn: Use NULL callback by default #5062

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
Sep 28, 2017

Conversation

0xc0170
Copy link
Contributor

@0xc0170 0xc0170 commented Sep 9, 2017

As we can check if callback was attached, we use NULL assignment.

Just a cosmetic change, that follows what we did for other attach() drivers.

@sg- @geky

As we can check if callback was attached, we use NULL assigment.
@0xc0170
Copy link
Contributor Author

0xc0170 commented Sep 19, 2017

cc @pan- @c1728p9 Please review

@theotherjimmy theotherjimmy changed the title InterruptIn: callback to NULL InterruptIn: Use NULL callback by default Sep 21, 2017
@0xc0170
Copy link
Contributor Author

0xc0170 commented Sep 27, 2017

/morph test

1 similar comment
@studavekar
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: 1417

All builds and test passed!

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.

7 participants