History

input: don't use recursive mutex

Previous commits made sure that the lock will never be called for more than once for all public functions. Thus deadlock is impossible, so recursive mutex is unneeded and can be converted to a normal mutex.

nanahi committed 2 years ago

Commit f4db4aa1 parent e8b94761 file · +1 −1Browse files

Unified · Split

input/input.c+1−1
@@ -1351,7 +1351,7 @@ struct input_ctx *mp_input_init(struct mpv_global *global, · 1350 unmodified lines
1351 1351
1352 ictx->opts = ictx->opts_cache->opts;1352 ictx->opts = ictx->opts_cache->opts;
1353 1353
1354 mp_mutex_init_type(&ictx->mutex, MP_MUTEX_RECURSIVE);1354 mp_mutex_init(&ictx->mutex);
1355 1355
1356 // Setup default section, so that it does nothing.1356 // Setup default section, so that it does nothing.
1357 mp_input_enable_section(ictx, NULL, MP_INPUT_ALLOW_VO_DRAGGING |1357 mp_input_enable_section(ictx, NULL, MP_INPUT_ALLOW_VO_DRAGGING |

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t