From: Jan Kiszka <jan.kiszka@siemens.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Dietmar Maurer <dietmar@proxmox.com>,
"Gabriel L. Somlo" <gsomlo@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] Reorder alarm timer setup again
Date: Thu, 22 Nov 2012 16:55:43 +0100 [thread overview]
Message-ID: <50AE4AFF.2030005@siemens.com> (raw)
In-Reply-To: <20121122130720.1b2293df@doriath.home>
On 2012-11-22 16:07, Luiz Capitulino wrote:
> On Thu, 01 Nov 2012 17:25:24 +0100
> Jan Kiszka <jan.kiszka@web.de> wrote:
>
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> ac4119c023 moved the alarm timer initialization to an earlier point but
>> failed to consider that it depends on qemu_init_main_loop. Instead of
>> moving the wrong things before os_daemonize, better push alarm timer
>> right after qemu_init_main_loop and move the chardev initialization
>> after this.
>
> Jan, it seems that you have to rebase this patch.
This issue was fixed indirectly by an already merged changeset of Paolo
- IIRC now.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2012-11-22 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.722719.1351782362.854.qemu-devel@nongnu.org>
2012-11-01 15:21 ` [Qemu-devel] monitor/qmp no longer working with -enable-kvm Gabriel L. Somlo
2012-11-01 16:25 ` [Qemu-devel] [PATCH] Reorder alarm timer setup again Jan Kiszka
2012-11-22 15:07 ` Luiz Capitulino
2012-11-22 15:55 ` Jan Kiszka [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=50AE4AFF.2030005@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=aliguori@us.ibm.com \
--cc=dietmar@proxmox.com \
--cc=gsomlo@gmail.com \
--cc=lcapitulino@redhat.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).