avoid dubiously clever code in win32_start_timer
commit9aea10297f34c33ee2225426c12be474a797a13b
authorPaolo Bonzini <pbonzini@redhat.com>
Wed, 10 Mar 2010 10:38:38 +0000 (10 11:38 +0100)
committerAnthony Liguori <aliguori@us.ibm.com>
Wed, 17 Mar 2010 16:14:52 +0000 (17 11:14 -0500)
tree13fb7558bf4b1d732f01640312f7ff30068dc01a
parent6d0ee85040e4d238e2483191fe6e74aebbecd5d5
avoid dubiously clever code in win32_start_timer

The code is initializing an unsigned int to UINT_MAX using "-1", so that
the following always-true comparison seems to be always-false at a
first look.  Since alarm timer initializations are never nested, it is
simpler to unconditionally store the result of timeGetDevCaps into
data->period.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
vl.c