[mutter] udev: Fix wrong closure function usage for the "device-added" signal

[Jonas Ådahl <jadahl src gnome org>]

commit 17c217848d7b80d3b23924812666267705fb0253
Author: Hans de Goede <hdegoede redhat com>
Date:   Fri Aug 2 21:20:04 2019 +0200

    udev: Fix wrong closure function usage for the "device-added" signal
    
    The "device-added" signal should use g_cclosure_marshal_VOID__OBJECT not
    g_cclosure_marshal_VOID__VOID.
    
    Instead of fixing this manually, simply replace the closure function for
    both signals with NULL, glib will then automatically set the correct
    va_marshaller.
    
    https://gitlab.gnome.org/GNOME/mutter/merge_requests/713

 src/backends/native/meta-udev.c | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)
---
diff --git a/src/backends/native/meta-udev.c b/src/backends/native/meta-udev.c
index ee7cc3ad4..719466131 100644
--- a/src/backends/native/meta-udev.c
+++ b/src/backends/native/meta-udev.c
@@ -212,15 +212,13 @@ meta_udev_class_init (MetaUdevClass *klass)
     g_signal_new ("hotplug",
                   G_TYPE_FROM_CLASS (object_class),
                   G_SIGNAL_RUN_LAST,
-                  0, NULL, NULL,
-                  g_cclosure_marshal_VOID__VOID,
+                  0, NULL, NULL, NULL,
                   G_TYPE_NONE, 0);
   signals[DEVICE_ADDED] =
     g_signal_new ("device-added",
                   G_TYPE_FROM_CLASS (object_class),
                   G_SIGNAL_RUN_LAST,
-                  0, NULL, NULL,
-                  g_cclosure_marshal_VOID__VOID,
+                  0, NULL, NULL, NULL,
                   G_TYPE_NONE, 1,
                   G_UDEV_TYPE_DEVICE);
 }