Skip to content

Conversation

@matt001k
Copy link
Contributor

What changed?

Add BM OS abstraction for mutex creation.
Utilzes bm_semaphore_create for binary semaphores.
Renames instances of bm_semaphore_create to bm_mutex_create due 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_core have been renamed properly.

Checklist

  • Add or update unit tests for changed code
  • Ensure all submodules up to date. If this PR relies on changes in submodules, merge those PRs first, then point this PR at/after the merge commit
  • Ensure code is formatted correctly with clang-format. If there are large formatting changes, they should happen in a separate whitespace-only commit on this PR after all approvals.

@matt001k matt001k self-assigned this Aug 11, 2025
@matt001k matt001k added the chore Work that needs to be done but does not add any new functionality or fixes a bug label Aug 11, 2025
Copy link
Contributor

@victorsowa12 victorsowa12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@matt001k matt001k merged commit 3fb6434 into main Aug 11, 2025
3 checks passed
@matt001k matt001k deleted the feature/mutex_abstraction branch August 11, 2025 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chore Work that needs to be done but does not add any new functionality or fixes a bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants