qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Tiejun Chen <tiejun.chen@intel.com>,
	qemu-devel@nongnu.org, Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH] qom-test: blacklist xenigd
Date: Sun, 17 Aug 2014 10:56:24 +0200	[thread overview]
Message-ID: <20140817085624.GB21143@redhat.com> (raw)
In-Reply-To: <53EE3646.3020903@suse.de>

On Fri, Aug 15, 2014 at 06:33:10PM +0200, Andreas Färber wrote:
> Am 14.08.2014 18:02, schrieb Michael S. Tsirkin:
> > Patch
> >     xen:hw:i386:pc_piix: introduce new machine for IGD passthrough
> > adds a new machine type.
> > Blacklist it since it forces xen accel.
> > 
> > Cc: Tiejun Chen <tiejun.chen@intel.com>
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> >  tests/qom-test.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/tests/qom-test.c b/tests/qom-test.c
> > index 4246382..10799e2 100644
> > --- a/tests/qom-test.c
> > +++ b/tests/qom-test.c
> > @@ -16,7 +16,7 @@
> >  #include "qapi/qmp/types.h"
> >  
> >  static const char *blacklist_x86[] = {
> > -    "xenfv", "xenpv", NULL
> > +    "xenfv", "xenpv", "xenigd", NULL
> >  };
> >  
> >  static const struct {
> 
> Reviewed-by: Andreas Färber <afaerber@suse.de>
> 
> What's the status of that series? If it's not yet applied as I
> understood your response, then you could just squash it there.
> 
> Cheers,
> Andreas

I applied this in my tree.
To avoid breaking bisect, I made this this 1st patch
in the series.

> -- 
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

      reply	other threads:[~2014-08-17  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14 16:02 [Qemu-devel] [PATCH] qom-test: blacklist xenigd Michael S. Tsirkin
2014-08-15 16:33 ` Andreas Färber
2014-08-17  8:56   ` Michael S. Tsirkin [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=20140817085624.GB21143@redhat.com \
    --to=mst@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tiejun.chen@intel.com \
    /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).