qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org, berrange@redhat.com, mreitz@redhat.com,
	pbonzini@redhat.com, ldoktor@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 1/2] cli: Don't run early event loop if no --preconfig was specified
Date: Wed, 6 Jun 2018 09:22:47 +0200	[thread overview]
Message-ID: <20180606092247.54bd320d@redhat.com> (raw)
In-Reply-To: <20180605181246.GN7451@localhost.localdomain>

On Tue, 5 Jun 2018 15:12:46 -0300
Eduardo Habkost <ehabkost@redhat.com> wrote:

> On Tue, Jun 05, 2018 at 04:00:42PM +0200, Igor Mammedov wrote:
> [...]
> > Based on
> >   From: Michal Privoznik <mprivozn@redhat.com>
> >   Subject: [PATCH] cli: Don't run early event loop if no --preconfig was specified
> >   Message-Id: <ad910973c593c5ac2fed3a10ea958f7e9c12f82c.1527935663.git.mprivozn@redhat.com>  
> 
> Michal's patch is already queued on machine-next.  It should be
> dropped if this patch gets included, correct?
> 
yep, it should be dropped as it has migrations issues.

  reply	other threads:[~2018-06-06  7:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05 14:00 [Qemu-devel] [PATCH v3 0/2] fix -nodefaults and -daemonize regressions caused by --preconfig introduction Igor Mammedov
2018-06-05 14:00 ` [Qemu-devel] [PATCH v3 1/2] cli: Don't run early event loop if no --preconfig was specified Igor Mammedov
2018-06-05 18:12   ` Eduardo Habkost
2018-06-06  7:22     ` Igor Mammedov [this message]
2018-06-11 17:34       ` Eduardo Habkost
2018-06-05 14:00 ` [Qemu-devel] [PATCH v3 2/2] vl: fix use of --daemonize with --preconfig Igor Mammedov
2018-06-05 15:13   ` Eric Blake
2018-06-05 15:28     ` [Qemu-devel] [PATCH v4 " Igor Mammedov
2018-06-05 18:30   ` [Qemu-devel] [PATCH v3 " Eduardo Habkost
2018-06-06  8:34     ` Igor Mammedov
2018-06-06  8:37     ` [Qemu-devel] [PATCH v5 " Igor Mammedov
2018-06-06 13:50       ` Eduardo Habkost
2018-06-07 12:00         ` [Qemu-devel] [PATCH v6 " Igor Mammedov
2018-06-08 13:21           ` Eduardo Habkost
2018-06-11 13:16             ` Igor Mammedov
2018-06-11 19:06               ` Eduardo Habkost
2018-06-11 21:29                 ` Igor Mammedov
2018-06-11 22:36                   ` Eduardo Habkost
2018-06-12  9:17                     ` [Qemu-devel] [libvirt] " Michal Privoznik
2018-06-12 12:42                       ` Igor Mammedov
2018-06-12 12:50                         ` Daniel P. Berrangé
2018-06-13 14:17                           ` Eduardo Habkost
2018-06-13 14:23                             ` Daniel P. Berrangé
2018-06-13 17:09                               ` Eduardo Habkost
2018-06-14 12:32                                 ` Igor Mammedov
2018-06-12 13:04                         ` Michal Privoznik
2018-06-12 13:10                           ` Peter Krempa
2018-06-12 13:17                           ` Daniel P. Berrangé
2018-06-06  8:55 ` [Qemu-devel] [PATCH v3 0/2] fix -nodefaults and -daemonize regressions caused by --preconfig introduction no-reply

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=20180606092247.54bd320d@redhat.com \
    --to=imammedo@redhat.com \
    --cc=berrange@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=ldoktor@redhat.com \
    --cc=mreitz@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).