qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH 14/15] Use gcc warning flag -Wempty-body, fix warnings
Date: Sun, 5 Sep 2010 19:24:26 +0000	[thread overview]
Message-ID: <AANLkTi=zbPTUadP8gmV1ouUAzc0DBfY9q4TTjmARVBjC@mail.gmail.com> (raw)
In-Reply-To: <20100905175456.GA24336@redhat.com>

On Sun, Sep 5, 2010 at 5:54 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
> On Sun, Sep 05, 2010 at 03:07:23PM +0000, Blue Swirl wrote:
>> diff --git a/hw/pxa2xx.c b/hw/pxa2xx.c
>> index 88f61c0..6e04645 100644
>> --- a/hw/pxa2xx.c
>> +++ b/hw/pxa2xx.c
>> @@ -1877,8 +1877,9 @@ static void pxa2xx_fir_write(void *opaque,
>> target_phys_addr_t addr,
>>          s->control[0] = value;
>>          if (!(value & (1 << 4)))                     /* RXE */
>>              s->rx_len = s->rx_start = 0;
>> -        if (!(value & (1 << 3)))                     /* TXE */
>> -            /* Nop */;
>> +        if (!(value & (1 << 3))) {                      /* TXE */
>> +            /* Nop */
>> +        }
>
> Should we change the surrounding code to use {} to keep it consistent?
> It's annoying to have {} in one place only.

In other reviews, changes like that have been called unrelated.

>
>>          s->enable = value & 1;                               /* ITR */
>>          if (!s->enable)
>>              s->status[0] = 0;
>

      reply	other threads:[~2010-09-05 19:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-05 15:07 [Qemu-devel] [PATCH 14/15] Use gcc warning flag -Wempty-body, fix warnings Blue Swirl
2010-09-05 17:54 ` [Qemu-devel] " Michael S. Tsirkin
2010-09-05 19:24   ` Blue Swirl [this message]

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='AANLkTi=zbPTUadP8gmV1ouUAzc0DBfY9q4TTjmARVBjC@mail.gmail.com' \
    --to=blauwirbel@gmail.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).