Jouni Malinen 7cc5995845 Skip D-Bus signals if the dbus_path is not yet set ... This avoids an invalid D-Bus call during interface initialization. The wpa_state change can happen before the D-Bus interface is set up, so we must be preparted to handle this early event signal. In theory, it should be possible to reorder initialization code to make sure D-Bus signals are ready, but that would likely require quite a bit of code restructuring, so it looks like a safer option for now is to just skip the early event.		2010-05-23 20:23:11 +03:00
..
.gitignore
dbus-wpa_supplicant.conf
dbus_common.c
dbus_common.h
dbus_common_i.h
dbus_dict_helpers.c
dbus_dict_helpers.h
dbus_new.c	Skip D-Bus signals if the dbus_path is not yet set	2010-05-23 20:23:11 +03:00
dbus_new.h
dbus_new_handlers.c	dbus: Add new KeyMgmt interface capabilities	2010-04-11 21:37:28 +03:00
dbus_new_handlers.h
dbus_new_handlers_wps.c
dbus_new_helpers.c
dbus_new_helpers.h
dbus_new_introspect.c
dbus_old.c	Skip D-Bus signals if the dbus_path is not yet set	2010-05-23 20:23:11 +03:00
dbus_old.h
dbus_old_handlers.c
dbus_old_handlers.h
dbus_old_handlers_wps.c
fi.epitest.hostap.WPASupplicant.service
fi.w1.wpa_supplicant1.service
Makefile