[evolution-data-server] CamelTransport: Use the internal 'send_lock' mutex directly.

[Matthew Barnes <mbarnes src gnome org>]

commit a2355328057512504f76d6564c4f6fcfa60c2e6c
Author: Matthew Barnes <mbarnes redhat com>
Date:   Sun Sep 22 09:01:50 2013 -0400

    CamelTransport: Use the internal 'send_lock' mutex directly.

 camel/camel-transport.c |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/camel/camel-transport.c b/camel/camel-transport.c
index 8511e69..20888f1 100644
--- a/camel/camel-transport.c
+++ b/camel/camel-transport.c
@@ -253,11 +253,11 @@ camel_transport_send_to_sync (CamelTransport *transport,
        class = CAMEL_TRANSPORT_GET_CLASS (transport);
        g_return_val_if_fail (class->send_to_sync != NULL, FALSE);
 
-       camel_transport_lock (transport, CAMEL_TRANSPORT_SEND_LOCK);
+       g_mutex_lock (&transport->priv->send_lock);
 
        /* Check for cancellation after locking. */
        if (g_cancellable_set_error_if_cancelled (cancellable, error)) {
-               camel_transport_unlock (transport, CAMEL_TRANSPORT_SEND_LOCK);
+               g_mutex_unlock (&transport->priv->send_lock);
                return FALSE;
        }
 
@@ -265,7 +265,7 @@ camel_transport_send_to_sync (CamelTransport *transport,
                transport, message, from, recipients, cancellable, error);
        CAMEL_CHECK_GERROR (transport, send_to_sync, success, error);
 
-       camel_transport_unlock (transport, CAMEL_TRANSPORT_SEND_LOCK);
+       g_mutex_unlock (&transport->priv->send_lock);
 
        return success;
 }