From 0d3975b556717449bc02b3592b6780168f0a3f25 Mon Sep 17 00:00:00 2001
From: Federico Mena Quintero <federico@gnome.org>
Date: Tue, 27 May 2025 15:11:31 -0600
Subject: [PATCH] core/calendar: Replace a manual GMutexLocker with
 G_MUTEX_AUTO_LOCK()

This takes care of static-scan's warning about a variable being set
but never read.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/581>
---
 src/core/gcal-calendar.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/src/core/gcal-calendar.c b/src/core/gcal-calendar.c
index de52131d..9a2fc45f 100644
--- a/src/core/gcal-calendar.c
+++ b/src/core/gcal-calendar.c
@@ -203,11 +203,10 @@ on_source_name_changed_cb (ESource      *source,
                            GParamSpec   *pspec,
                            GcalCalendar *self)
 {
-  g_autoptr (GMutexLocker) locker = NULL;
   GcalCalendarPrivate *priv;
 
   priv = gcal_calendar_get_instance_private (self);
-  locker = g_mutex_locker_new (&priv->shared.mutex);
+  G_MUTEX_AUTO_LOCK (&priv->shared.mutex, locker);
 
   priv->shared.name_changed = TRUE;
   schedule_idle_update_unlocked (self);