qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Cao jin <caoj.fnst@cn.fujitsu.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH] main-loop: check return value before using
Date: Wed, 6 Jul 2016 14:46:50 +0800	[thread overview]
Message-ID: <20160706064650.GB16605@ad.usersys.redhat.com> (raw)
In-Reply-To: <1467774199-21807-1-git-send-email-caoj.fnst@cn.fujitsu.com>

On Wed, 07/06 11:03, Cao jin wrote:
> pointer 'qemu_aio_context' should be checked first before it is used.
> qemu_bh_new() will use it.
> 
> Also add extra newlines to make code well separated and easier to read.

This "also" is not good, please only do one thing in a patch.

Fam

> 
> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
> ---
>  main-loop.c | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/main-loop.c b/main-loop.c
> index 89a6994..0d943f1 100644
> --- a/main-loop.c
> +++ b/main-loop.c
> @@ -154,18 +154,23 @@ int qemu_init_main_loop(Error **errp)
>      }
>  
>      qemu_aio_context = aio_context_new(&local_error);
> -    qemu_notify_bh = qemu_bh_new(notify_event_cb, NULL);
>      if (!qemu_aio_context) {
>          error_propagate(errp, local_error);
>          return -EMFILE;
>      }
> +
> +    qemu_notify_bh = qemu_bh_new(notify_event_cb, NULL);
> +
>      gpollfds = g_array_new(FALSE, FALSE, sizeof(GPollFD));
> +
>      src = aio_get_g_source(qemu_aio_context);
>      g_source_attach(src, NULL);
>      g_source_unref(src);
> +
>      src = iohandler_get_g_source();
>      g_source_attach(src, NULL);
>      g_source_unref(src);
> +
>      return 0;
>  }
>  
> -- 
> 2.1.0
> 
> 
> 
> 

  parent reply	other threads:[~2016-07-06  6:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06  3:03 [Qemu-devel] [PATCH] main-loop: check return value before using Cao jin
2016-07-06  5:28 ` Cao jin
2016-07-06  6:46 ` Fam Zheng [this message]
2016-07-06  7:46   ` Cao jin
2016-07-07  0:31     ` Fam Zheng
2016-07-07  3:18       ` Cao jin
2016-07-07  5:00         ` Fam Zheng

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=20160706064650.GB16605@ad.usersys.redhat.com \
    --to=famz@redhat.com \
    --cc=caoj.fnst@cn.fujitsu.com \
    --cc=pbonzini@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).