diff options
| author | wm4 <wm4@nowhere> | 2014-06-08 16:11:39 +0200 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2014-06-08 16:11:39 +0200 |
| commit | 09dd1ed47cbd6ea1e626b6bc2bfafa3af7d11cce (patch) | |
| tree | f1d05b29432cffafbef201215d57332a87ae8425 /player | |
| parent | 51834592fc59325d6276feb4f35a373985fc7fdd (diff) | |
| download | mpv-09dd1ed47cbd6ea1e626b6bc2bfafa3af7d11cce.tar.bz2 mpv-09dd1ed47cbd6ea1e626b6bc2bfafa3af7d11cce.tar.xz | |
client API: minor documentation fixes/enhancements
Diffstat (limited to 'player')
| -rw-r--r-- | player/client.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/player/client.c b/player/client.c index c375a11d94..56b7029a42 100644 --- a/player/client.c +++ b/player/client.c @@ -42,9 +42,9 @@ /* * Locking hierarchy: * - * MPContext > mp_client_api.lock > mpv_handle.lock + * MPContext > mp_client_api.lock > mpv_handle.lock > * > mpv_handle.wakeup_lock * - * MPContext strictly speaking has no locks, and instead implicitly managed + * MPContext strictly speaking has no locks, and instead is implicitly managed * by MPContext.dispatch, which basically stops the playback thread at defined * points in order to let clients access it in a synchronized manner. Since * MPContext code accesses the client API, it's on top of the lock hierarchy. |