common: adjust mainloop notification callbacks to dominant usage patterns
authorKrisztian Litkey <krisztian.litkey@intel.com>
Thu, 28 Mar 2013 09:30:47 +0000 (11:30 +0200)
committerKrisztian Litkey <krisztian.litkey@intel.com>
Thu, 28 Mar 2013 12:58:21 +0000 (14:58 +0200)
commitcef30e128e33c64c52f8a3e1717cacf185113a9d
treec9af935fd7497ac7933061ceb1f567c811d98fe0
parent563f8e10934e1c4eb54a8fb3afe8cdd865bb8214
common: adjust mainloop notification callbacks to dominant usage patterns

Since practically none of the notification callbacks used the first
mainloop argument, it is not passed to the callbacks any more. Instead
mrp_get_*_mainloop getter functions has been added for retrieving the
mainloop pointer associated with the various objects for those few
cases where this is necessary.
24 files changed:
src/breedline/breedline-murphy.c
src/common/dbus-glue.c
src/common/dgram-transport.c
src/common/internal-transport.c
src/common/mainloop.c
src/common/mainloop.h
src/common/process.c
src/common/stream-transport.c
src/common/tests/dbus-pump.c
src/common/tests/dbus-test.c
src/common/tests/internal-transport-test.c
src/common/tests/mainloop-test.c
src/common/tests/transport-test.c
src/common/transport.c
src/common/websocklib.c
src/console-client/client.c
src/daemon/daemon.c
src/plugins/domain-control/client.c
src/plugins/domain-control/domain-control.c
src/plugins/domain-control/test-client.c
src/plugins/plugin-dbus.c
src/plugins/resource-native/libmurphy-resource/api_test.c
src/plugins/resource-native/resource-client.c
src/resolver/target.c