mirror of
https://github.com/libvirt/libvirt.git
synced 2025-02-25 18:55:26 -06:00
Rename domain lifecycle event message
To avoid confusion, rename the current REMOTE_PROC_DOMAIN_EVENT message to REMOTE_PROC_DOMAIN_EVENT_LIFECYCLE. This does not cause ABI problems, since the names are only relevant at the source code level. On the wire they encoding is a plain integer whose value does not change * src/remote/remote_protocol.x: Rename REMOTE_PROC_DOMAIN_EVENT to REMOTE_PROC_DOMAIN_EVENT_LIFECYCLE. * daemon/remote.c, src/remote/remote_driver.c: Update code for renamed event
This commit is contained in:
@@ -105,7 +105,7 @@ static int remoteRelayDomainEventLifecycle(virConnectPtr conn ATTRIBUTE_UNUSED,
|
||||
void *opaque)
|
||||
{
|
||||
struct qemud_client *client = opaque;
|
||||
remote_domain_event_msg data;
|
||||
remote_domain_event_lifecycle_msg data;
|
||||
|
||||
if (!client)
|
||||
return -1;
|
||||
@@ -121,8 +121,8 @@ static int remoteRelayDomainEventLifecycle(virConnectPtr conn ATTRIBUTE_UNUSED,
|
||||
data.detail = detail;
|
||||
|
||||
remoteDispatchDomainEventSend (client,
|
||||
REMOTE_PROC_DOMAIN_EVENT,
|
||||
(xdrproc_t)xdr_remote_domain_event_msg, &data);
|
||||
REMOTE_PROC_DOMAIN_EVENT_LIFECYCLE,
|
||||
(xdrproc_t)xdr_remote_domain_event_lifecycle_msg, &data);
|
||||
|
||||
virMutexUnlock(&client->lock);
|
||||
|
||||
|
||||
Reference in New Issue
Block a user