From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, prashanth sunder <prashanth.sunder@gmail.com>
Subject: Re: [Qemu-devel] [PATCH 6/6] main: set names for main loop sources created
Date: Mon, 3 Oct 2016 16:19:28 +0100 [thread overview]
Message-ID: <20161003151928.GS10245@stefanha-x1.localdomain> (raw)
In-Reply-To: <1475248620-534-7-git-send-email-berrange@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 336 bytes --]
On Fri, Sep 30, 2016 at 04:17:00PM +0100, Daniel P. Berrange wrote:
> The main loop creates two generic sources for the AIO
> and IO handler systems.
>
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
> main-loop.c | 2 ++
> 1 file changed, 2 insertions(+)
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2016-10-03 15:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 15:16 [Qemu-devel] [PATCH 0/6] Give names to all GSources QEMU creates Daniel P. Berrange
2016-09-30 15:16 ` [Qemu-devel] [PATCH 1/6] io: add ability to set a name for IO channels Daniel P. Berrange
2016-09-30 18:41 ` Eric Blake
2016-09-30 15:16 ` [Qemu-devel] [PATCH 2/6] nbd: set name for all I/O channels created Daniel P. Berrange
2016-09-30 16:12 ` Paolo Bonzini
2016-10-03 15:15 ` Stefan Hajnoczi
2016-09-30 15:16 ` [Qemu-devel] [PATCH 3/6] char: " Daniel P. Berrange
2016-09-30 16:12 ` Paolo Bonzini
2016-10-03 15:18 ` Stefan Hajnoczi
2016-09-30 15:16 ` [Qemu-devel] [PATCH 4/6] migration: " Daniel P. Berrange
2016-10-03 15:18 ` Stefan Hajnoczi
2016-09-30 15:16 ` [Qemu-devel] [PATCH 5/6] vnc: " Daniel P. Berrange
2016-10-03 15:19 ` Stefan Hajnoczi
2016-09-30 15:17 ` [Qemu-devel] [PATCH 6/6] main: set names for main loop sources created Daniel P. Berrange
2016-09-30 16:13 ` Paolo Bonzini
2016-10-03 15:19 ` Stefan Hajnoczi [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=20161003151928.GS10245@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=berrange@redhat.com \
--cc=prashanth.sunder@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 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).