diff options
| author | Tomas Bzatek <tbzatek@redhat.com> | 2012-12-10 15:18:04 +0100 |
|---|---|---|
| committer | Tomas Bzatek <tbzatek@redhat.com> | 2012-12-10 15:18:04 +0100 |
| commit | ee170849f84ecb09caf6dc49611db9db812f060c (patch) | |
| tree | 17f83ce663a6f5c3f3874d1546178baced183ad9 | |
| parent | 3c08836f7f9cb61317298e85c1fe6adee01860aa (diff) | |
| download | gvfs-ee170849f84ecb09caf6dc49611db9db812f060c.tar.gz | |
proxy volume monitor: Clarify when mutex is hold on construction
Found by reviewing usage of the global lock, this place is not obvious
whether is inside the lock or not. Let's add a simple comment to make it
clear.
| -rw-r--r-- | monitor/proxy/gproxyvolumemonitor.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/monitor/proxy/gproxyvolumemonitor.c b/monitor/proxy/gproxyvolumemonitor.c index d21da7fc..823c1689 100644 --- a/monitor/proxy/gproxyvolumemonitor.c +++ b/monitor/proxy/gproxyvolumemonitor.c @@ -1088,6 +1088,7 @@ dispose_in_idle (gpointer object) g_idle_add ((GSourceFunc) dispose_in_idle_do, g_object_ref (object)); } +/* Typically called from g_proxy_volume_monitor_constructor() with proxy_vm lock being held */ static void g_proxy_volume_monitor_init (GProxyVolumeMonitor *monitor) { |