Re: [libvirt] [PATCH] Pull DBus event code out into common area

2012-04-12 Thread Daniel P. Berrange
On Thu, Apr 12, 2012 at 02:05:44PM -0600, Eric Blake wrote: > Did you forget to squash this into a prior patch? The commit message > mentions a new file virdbus.h that I don't see here, and since I don't > have virdbus.c, this patch won't apply. Urgh, yes. Squashed & resent Daniel -- |: http://

Re: [libvirt] [PATCH] Pull DBus event code out into common area

2012-04-12 Thread Eric Blake
On 04/12/2012 01:14 PM, Daniel P. Berrange wrote: > From: "Daniel P. Berrange" > > The policy kit and HAL node device drivers both require a > DBus connection. The HAL device code further requires that > the DBus connection is integrated with the event loop and > provides such glue logic itself.

[libvirt] [PATCH] Pull DBus event code out into common area

2012-04-12 Thread Daniel P. Berrange
From: "Daniel P. Berrange" The policy kit and HAL node device drivers both require a DBus connection. The HAL device code further requires that the DBus connection is integrated with the event loop and provides such glue logic itself. The forthcoming FirewallD integration also requires a dbus co