cpu/cc2538: Remove superfluous mutex lock #5804
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
OlegHahm
added
Platform: ARM
aeneby
force-pushed
the
no_mutex_lock
branch
from
72f72ef to
2ba43d5
Compare
|
Fine by me 👍 |
alignan
added
the
CI: ready for build
PeterKietzmann
approved these changes
Sep 26, 2016
|
ACK and go |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
AFAICT, these mutex locks are unnecessary and simply introduce delays. The sequential nature of RIOT's packet handling and the TX_ACTIVE wait in send() should be enough to ensure exclusivity.