From: Avi Kivity <avi@qumranet.com>
To: Alexander Graf <alex@csgraf.de>
Cc: kvm-devel@lists.sourceforge.net,
Carlo Marcelo Arenas Belon <carenas@sajinet.com.pe>
Subject: Re: [PATCH] qemu: implicit precedence for logical operator in has_work
Date: Sun, 24 Feb 2008 11:59:41 +0200 [thread overview]
Message-ID: <47C1400D.2020103@qumranet.com> (raw)
In-Reply-To: <DD132EF1-BE23-4F82-89AF-13242529BA21@csgraf.de>
Alexander Graf wrote:
> On Feb 20, 2008, at 9:30 AM, Carlo Marcelo Arenas Belon wrote:
>
>
>> janitorial fix for :
>>
>> qemu/qemu-kvm.c: In function `has_work':
>> qemu/qemu-kvm.c:140: warning: suggest parentheses around && within ||
>>
>> Signed-off-by: Carlo Marcelo Arenas Belon <carenas@sajinet.com.pe>
>> ---
>> qemu/qemu-kvm.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/qemu/qemu-kvm.c b/qemu/qemu-kvm.c
>> index ffc59d5..4056453 100644
>> --- a/qemu/qemu-kvm.c
>> +++ b/qemu/qemu-kvm.c
>> @@ -137,7 +137,7 @@ extern int vm_running;
>>
>> static int has_work(CPUState *env)
>> {
>> - if (!vm_running || env && vcpu_info[env->cpu_index].stopped)
>> + if (!vm_running || (env && vcpu_info[env->cpu_index].stopped))
>>
>
> What exactly is the env check needed for here?
>
>
This code arrived from another location, where it was necessary.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-02-24 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 8:30 [PATCH] qemu: implicit precedence for logical operator in has_work Carlo Marcelo Arenas Belon
2008-02-20 8:23 ` Alexander Graf
2008-02-24 9:59 ` Avi Kivity [this message]
2008-02-24 9:58 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47C1400D.2020103@qumranet.com \
--to=avi@qumranet.com \
--cc=alex@csgraf.de \
--cc=carenas@sajinet.com.pe \
--cc=kvm-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox