Feature/mutex abstraction #106
Merged
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.
What changed?
Add BM OS abstraction for mutex creation.
Utilzes
bm_semaphore_createfor binary semaphores.Renames instances of
bm_semaphore_createtobm_mutex_createdue to the fact they are actually being used as mutexes.How does it make Bristlemouth better?
Create mutex under more direct API call to increase clarity when invoking the API.
Where should reviewers focus?
All files are important. Good to validate that all API in
bm_corehave been renamed properly.Checklist