Hi Andrew,

 >>>
>>> +uint32_t l_dbus_name_acquire(struct l_dbus *dbus, const char *name,
>>> +                               bool allow_replacement, bool
>>> replace_existing,
>>> +                               bool queue, l_dbus_name_acquire_func_t
>>> callback,
>>> +                               void *user_data);
>>> +
>>
>>
>> What's the uint32_t return for?
>
> So that the call can be cancelled with l_dbus_cancel if the user no
> longer needs the name and it is still waiting for the callback (should
> be rare).
>

The semantics are a bit weird here though.  You have kdbus version that 
simply returns 0.  dbus1 version returns a uint32 or 0 depending on 
success / failure.

How does the client application know what is what?  Perhaps a straight 
true/false might be better here?

Regards,
-Denis