From: Peter Maydell <peter.maydell@linaro.org>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [Qemu-devel] [PULL 0/1] Machine queue, 2018-06-11
Date: Tue, 12 Jun 2018 11:56:11 +0100 [thread overview]
Message-ID: <CAFEAcA83ZYsZB-yaaUFzddmG7ZKqV5oAq-6rnBobcMp9C-ddkQ@mail.gmail.com> (raw)
In-Reply-To: <20180611173452.28087-1-ehabkost@redhat.com>
On 11 June 2018 at 18:34, Eduardo Habkost <ehabkost@redhat.com> wrote:
> The following changes since commit 9f55925b8f50a962d1d08d815044db7767ae3838:
>
> Merge remote-tracking branch 'remotes/vivier/tags/m68k-for-3.0-pull-request' into staging (2018-06-11 12:46:16 +0100)
>
> are available in the Git repository at:
>
> git://github.com/ehabkost/qemu.git tags/machine-next-pull-request
>
> for you to fetch changes up to 0f5319ea25fb0a05827d512859b7c7d23371ac5d:
>
> cli: Don't run early event loop if no --preconfig was specified (2018-06-11 14:25:49 -0300)
>
> ----------------------------------------------------------------
> Machine queue, 2018-06-11
>
> * Fix -daemonize hang caused by --preconfig code
>
> ----------------------------------------------------------------
>
> Queue for Machine Core patches
>
>
> Igor Mammedov (1):
> cli: Don't run early event loop if no --preconfig was specified
>
> vl.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --
Applied, thanks.
-- PMM
prev parent reply other threads:[~2018-06-12 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 17:34 [Qemu-devel] [PULL 0/1] Machine queue, 2018-06-11 Eduardo Habkost
2018-06-11 17:34 ` [Qemu-devel] [PULL 1/1] cli: Don't run early event loop if no --preconfig was specified Eduardo Habkost
2018-06-12 10:56 ` Peter Maydell [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=CAFEAcA83ZYsZB-yaaUFzddmG7ZKqV5oAq-6rnBobcMp9C-ddkQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=marcel.apfelbaum@gmail.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).