All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: "Michael S. Tsirkin" <mst@redhat.com>, qemu-devel@nongnu.org
Cc: Tiejun Chen <tiejun.chen@intel.com>,
	Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH] qom-test: blacklist xenigd
Date: Fri, 15 Aug 2014 18:33:10 +0200	[thread overview]
Message-ID: <53EE3646.3020903@suse.de> (raw)
In-Reply-To: <1408032125-10596-1-git-send-email-mst@redhat.com>

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

-- 
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-15 16:33 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 [this message]
2014-08-17  8:56   ` Michael S. Tsirkin

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=53EE3646.3020903@suse.de \
    --to=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=mst@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.