-
Notifications
You must be signed in to change notification settings - Fork 7k
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
subsys: random: Correct Mutex define #86454
Conversation
53c671a
to
bb125f9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
samples:
in the commit message looks out of place?
bb125f9
to
fbd357c
Compare
just fixed it |
try again 😄 |
🍿 |
@tomi-font mm sorry, what am I missing? ![]() |
You have |
Correct Mutex ctr_lock defination as the wrong defination lead to sysworkq task not acquiring this mutex during bt init, which lead to BLE didn't work as described in issue zephyrproject-rtos#86444 Signed-off-by: Ying Zhang <ying.zhang_2@nxp.com>
fbd357c
to
7956946
Compare
First time contributors? I do it all the time :-) Pushed over this myself, let's how I messed up this time. |
@fabiobaltieri @tomi-font btw this basically means that something's wrong with Gitlint, as it should be catching it? Line 29 in fdb8b30
|
Correct Mutex ctr_lock defination as the wrong defination lead to sysworkq task not acquiring this mutex during bt init, which lead to BLE didn't work as described in issue #86444.