Re: [PATCH 3/7] Add 'detail' arg to network lifecycle event internals

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Dec 12, 2013 at 06:04:03PM +0000, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
>
> While the public API & wire protocol included the 'detail'
> arg for network lifecycle events, the internal event handling
> code did not process it. This meant that if a future libvirtd
> server starts sending non-0 'detail' args, the current libvirt
> client will not process them.
>
> Signed-off-by: Daniel P. Berrange <berrange@xxxxxxxxxx>
> ---
>  src/conf/network_event.c    |  7 +++++--
>  src/conf/network_event.h    |  3 ++-
>  src/network/bridge_driver.c | 15 ++++++++++-----
>  src/remote/remote_driver.c  |  2 +-
>  src/test/test_driver.c      | 15 ++++++++++-----
>  5 files changed, 28 insertions(+), 14 deletions(-)
>

ACK,

Martin

Attachment: signature.asc
Description: Digital signature

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]