All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Devin Nakamura <devin122@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] qemu-io: Fix if scoping bug
Date: Tue, 14 Jun 2011 10:42:02 +0200	[thread overview]
Message-ID: <m3r56werdx.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <BANLkTinvfuoOESXFiA1ndfwNadMP94xEaA@mail.gmail.com> (Devin Nakamura's message of "Fri, 10 Jun 2011 23:29:46 -0400")

Devin Nakamura <devin122@gmail.com> writes:

> Fix a bug caused by lack of braces in if statement

You describe the bug's cause.  That's good.  Please also describe the
bug's effect, i.e. what exactly is broken for users.

>
> Signed-off-by: Devin Nakamura <devin122@gmail.com>
> ---
>  qemu-io.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/qemu-io.c b/qemu-io.c
> index 53adb76..1c4f684 100644
> --- a/qemu-io.c
> +++ b/qemu-io.c
> @@ -433,12 +433,12 @@ static int read_f(int argc, char **argv)
>          return 0;
>      }
>
> -    if (!pflag)
> +    if (!pflag){

Put a space between ) and {

>          if (offset & 0x1ff) {
>              printf("offset %" PRId64 " is not sector aligned\n",
>                     offset);
>              return 0;
> -
> +        }
>          if (count & 0x1ff) {
>              printf("count %d is not sector aligned\n",
>                     count);

  reply	other threads:[~2011-06-14  8:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-11  3:29 [Qemu-devel] [PATCH 2/2] qemu-io: Fix if scoping bug Devin Nakamura
2011-06-14  8:42 ` Markus Armbruster [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-07-11  5:25 [Qemu-devel] [PATCH 1/2] qemu-io: Fix formatting Devin Nakamura
2011-07-11  5:25 ` [Qemu-devel] [PATCH 2/2] qemu-io: Fix if scoping bug Devin Nakamura
2011-07-11  9:47   ` Stefan Hajnoczi
2011-07-11 13:18     ` Kevin Wolf
2011-07-11 13:18       ` Stefan Hajnoczi

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=m3r56werdx.fsf@blackfin.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=devin122@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.