xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Tiejun Chen <tiejun.chen@intel.com>
Cc: pbonzini@redhat.com, xen-devel@lists.xensource.com,
	qemu-devel@nongnu.org, stefano.stabellini@eu.citrix.com
Subject: Re: [v5][PATCH 0/4] xen: introduce new machine for IGD passthrough
Date: Sun, 23 Nov 2014 12:10:47 +0200	[thread overview]
Message-ID: <20141123101047.GA3109@redhat.com> (raw)
In-Reply-To: <1407836957-29098-1-git-send-email-tiejun.chen@intel.com>

On Tue, Aug 12, 2014 at 05:49:13PM +0800, Tiejun Chen wrote:
> v5:
> 
> * Simplify to make sure its really inherited from the standard one in patch #3
> * Then drop the original patch #3

I carried
	i440fx: make types configurable at run-time
	pc_init1: pass parameters just with types
	xen:hw:pci-host:piix: create host bridge to passthrough
	qom-test: blacklist xenigd
	xen:hw:i386:pc_piix: introduce new machine for IGD passthrough

on my branch for a while now, but I'm not sure it's all still needed.
If yes simply include these patches next time you repost the
patchset.

-- 
MST

  parent reply	other threads:[~2014-11-23 10:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12  9:49 [v5][PATCH 0/4] xen: introduce new machine for IGD passthrough Tiejun Chen
2014-08-12  9:49 ` [v5][PATCH 1/4] i440fx: make types configurable at run-time Tiejun Chen
2014-08-12  9:49 ` [v5][PATCH 2/4] pc_init1: pass parameters just with types Tiejun Chen
2014-08-12  9:49 ` [v5][PATCH 3/4] xen:hw:pci-host:piix: create host bridge to passthrough Tiejun Chen
2014-08-12  9:49 ` [v5][PATCH 4/4] xen:hw:i386:pc_piix: introduce new machine for IGD passthrough Tiejun Chen
2014-08-14 16:03   ` Michael S. Tsirkin
2014-08-15  5:46     ` Chen, Tiejun
2014-08-14  0:59 ` [v5][PATCH 0/4] xen: " Chen, Tiejun
2014-08-14  7:09 ` Michael S. Tsirkin
2014-08-14  7:23   ` Chen, Tiejun
2014-11-23 10:10 ` Michael S. Tsirkin [this message]
2014-11-24  0:40   ` Chen, Tiejun

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=20141123101047.GA3109@redhat.com \
    --to=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tiejun.chen@intel.com \
    --cc=xen-devel@lists.xensource.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).