From: Ian Campbell <ian.campbell@citrix.com>
To: "Chen, Tiejun" <tiejun.chen@intel.com>
Cc: Ian.Jackson@eu.citrix.com, wei.liu2@citrix.com,
qemu-devel@nongnu.org, stefano.stabellini@citrix.com,
xen-devel@lists.xen.org
Subject: Re: [Qemu-devel] [v3][PATCH 2/2] libxl: introduce gfx_passthru_kind
Date: Wed, 1 Apr 2015 10:53:30 +0100 [thread overview]
Message-ID: <1427882010.2115.265.camel@citrix.com> (raw)
In-Reply-To: <551BB7F4.7040006@intel.com>
On Wed, 2015-04-01 at 17:18 +0800, Chen, Tiejun wrote:
> Currently Qemu maintainers are busy finalizing qemu 2.3, they don't
> complete to review all associated qemu patch set. Although that don't
> bring any change to our two patches on Xen side, I think we'd better
> merge these patches until qemu patches are really applied into qemu
> tree. So I will send this series again until we can really consume this
> with qemu upstream, right?
IOW I should put this to one side until you tell me the qemu side is in
place (by resending the series)? Fine by me, thanks.
> BTW, I really appreciate your all comments in this thread.
No problem, thanks for sticking with my nit picking.
Ian.
next prev parent reply other threads:[~2015-04-01 9:53 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 1:17 [Qemu-devel] [v3][PATCH 0/2] libxl: try to support IGD passthrough for qemu upstream Tiejun Chen
2015-03-23 1:17 ` [Qemu-devel] [v3][PATCH 1/2] libxl: introduce libxl__is_igd_vga_passthru Tiejun Chen
2015-03-23 1:17 ` Tiejun Chen
2015-03-23 1:17 ` [Qemu-devel] [v3][PATCH 2/2] libxl: introduce gfx_passthru_kind Tiejun Chen
2015-03-23 1:17 ` Tiejun Chen
2015-03-24 8:47 ` One question to lowlevel/xl/xl.c and lowlevel/xc/xc.c Chen, Tiejun
2015-03-24 8:47 ` [Qemu-devel] " Chen, Tiejun
2015-03-24 9:51 ` Ian Campbell
2015-03-24 9:51 ` [Qemu-devel] " Ian Campbell
2015-03-24 10:15 ` Chen, Tiejun
2015-03-24 10:20 ` Ian Campbell
2015-03-24 10:31 ` Chen, Tiejun
2015-03-24 10:40 ` Ian Campbell
2015-03-25 1:18 ` Chen, Tiejun
2015-03-25 10:26 ` Ian Campbell
2015-03-25 10:26 ` [Qemu-devel] " Ian Campbell
2015-03-26 0:44 ` Chen, Tiejun
2015-03-26 0:44 ` [Qemu-devel] " Chen, Tiejun
2015-03-25 1:18 ` Chen, Tiejun
2015-03-24 10:40 ` Ian Campbell
2015-03-24 10:31 ` Chen, Tiejun
2015-03-24 10:20 ` Ian Campbell
2015-03-24 10:15 ` Chen, Tiejun
2015-03-24 14:50 ` [Qemu-devel] [v3][PATCH 2/2] libxl: introduce gfx_passthru_kind Ian Campbell
2015-03-25 1:10 ` Chen, Tiejun
2015-03-25 1:10 ` [Qemu-devel] " Chen, Tiejun
2015-03-25 10:32 ` Ian Campbell
2015-03-26 0:53 ` Chen, Tiejun
2015-03-26 10:06 ` Ian Campbell
2015-03-26 10:06 ` [Qemu-devel] " Ian Campbell
2015-03-27 1:29 ` Chen, Tiejun
2015-03-27 1:29 ` [Qemu-devel] " Chen, Tiejun
2015-03-27 9:54 ` Ian Campbell
2015-03-30 1:28 ` Chen, Tiejun
2015-03-30 1:28 ` [Qemu-devel] " Chen, Tiejun
2015-03-30 9:19 ` Ian Campbell
2015-04-01 1:05 ` Chen, Tiejun
2015-04-01 8:45 ` Ian Campbell
2015-04-01 8:45 ` [Qemu-devel] " Ian Campbell
2015-04-01 9:18 ` Chen, Tiejun
2015-04-01 9:18 ` [Qemu-devel] " Chen, Tiejun
2015-04-01 9:53 ` Ian Campbell [this message]
2015-04-01 9:53 ` Ian Campbell
2015-04-01 1:05 ` Chen, Tiejun
2015-03-30 9:19 ` Ian Campbell
2015-03-27 9:54 ` Ian Campbell
2015-03-26 0:53 ` Chen, Tiejun
2015-03-25 10:32 ` Ian Campbell
2015-03-24 14:50 ` Ian Campbell
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=1427882010.2115.265.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@citrix.com \
--cc=tiejun.chen@intel.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 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.