[libvirt] [PATCH 2/2] qemu: Drop word "either" from comments for agent monitor functions
Osier Yang
jyang at redhat.com
Wed Nov 28 12:51:24 UTC 2012
On 2012年11月28日 20:35, Peter Krempa wrote:
> ---
> src/qemu/qemu_domain.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/src/qemu/qemu_domain.c b/src/qemu/qemu_domain.c
> index 92f4a3e..78ebe9f 100644
> --- a/src/qemu/qemu_domain.c
> +++ b/src/qemu/qemu_domain.c
> @@ -1162,9 +1162,9 @@ qemuDomainObjExitAgentInternal(struct qemud_driver *driver,
> /*
> * obj must be locked before calling, qemud_driver must be unlocked
> *
> - * To be called immediately before any QEMU agent API call
> - * Must have already either called qemuDomainObjBeginJob() and checked
> - * that the VM is still active;
> + * To be called immediately before any QEMU agent API call.
> + * Must have already called qemuDomainObjBeginJob() and checked
> + * that the VM is still active.
> *
> * To be followed with qemuDomainObjExitAgent() once complete
> */
> @@ -1187,8 +1187,8 @@ void qemuDomainObjExitAgent(struct qemud_driver *driver,
> /*
> * obj must be locked before calling, qemud_driver must be locked
> *
> - * To be called immediately before any QEMU agent API call
> - * Must have already either called qemuDomainObjBeginJobWithDriver() and
> + * To be called immediately before any QEMU agent API call.
> + * Must have already called qemuDomainObjBeginJobWithDriver() and
> * checked that the VM is still active; may not be used for nested async jobs.
> *
> * To be followed with qemuDomainObjExitAgentWithDriver() once complete
ACK.
More information about the libvir-list
mailing list