summaryrefslogtreecommitdiff
path: root/atspi/atspi-event-listener.c
diff options
context:
space:
mode:
authorFederico Mena Quintero <federico@gnome.org>2022-06-01 13:16:17 -0500
committerFederico Mena Quintero <federico@gnome.org>2022-06-02 16:26:07 -0500
commitfbba144f52c52c1f331b93dd4225d115ebf04630 (patch)
treeb2e7c1be997b590d4ff41a52631d856f27b07c00 /atspi/atspi-event-listener.c
parent6bec005915c4562a17608b0ea3726c9f6cbffc7c (diff)
downloadat-spi2-core-fbba144f52c52c1f331b93dd4225d115ebf04630.tar.gz
Remove unused field BusDataClosure.data
The comment "TODO this is still memory leak on c->data" from destroy_deferred_message_item() caught my eye, so I went looking for what uses it. defer_message() is the only place that creates BusDataClosure structs, and gets passed the data field. However, the only caller of defer_message() is dbus_connection_add_filter(), and *that* call is done with both NULL user_data and free_data_function. So, defer_message() will always get data=NULL. This commit also removes all the "void *user_data" arguments from the functions called by process_deferred_message(); they just got passed the closure->data but none of them actually use it.
Diffstat (limited to 'atspi/atspi-event-listener.c')
-rw-r--r--atspi/atspi-event-listener.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/atspi/atspi-event-listener.c b/atspi/atspi-event-listener.c
index 5cdc8064..b4a07af4 100644
--- a/atspi/atspi-event-listener.c
+++ b/atspi/atspi-event-listener.c
@@ -965,7 +965,7 @@ _atspi_send_event (AtspiEvent *e)
}
DBusHandlerResult
-_atspi_dbus_handle_event (DBusConnection *bus, DBusMessage *message, void *data)
+_atspi_dbus_handle_event (DBusConnection *bus, DBusMessage *message)
{
char *detail = NULL;
const char *category = dbus_message_get_interface (message);