From: Christoph Egger <Christoph.Egger@amd.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH] stubdom/minios: re-structure headers part 1/2
Date: Wed, 30 Sep 2009 17:45:24 +0200 [thread overview]
Message-ID: <200909301745.24829.Christoph.Egger@amd.com> (raw)
In-Reply-To: <C6E92209.1617E%keir.fraser@eu.citrix.com>
On Wednesday 30 September 2009 15:56:09 Keir Fraser wrote:
> On 30/09/2009 11:39, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
> > The two patches change the include path, first one in xen-tree, second
> > one in ioemu tree. It is necessary to have both upstream *before* the
> > real header restructuring or build breaks, otherwise.
>
> Do both patches need to be applied at the same time? Can I check in the Xen
> patch before the qemu patch, or will that break the build?
The two patches can be applied independent from each other.
I haven't submitted the patch yet which does the real header restructuring.
That one depends on having both patches applied first to not break the build.
Christoph
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Andrew Bowd, Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
prev parent reply other threads:[~2009-09-30 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 10:39 [PATCH] stubdom/minios: re-structure headers part 1/2 Christoph Egger
2009-09-30 10:50 ` Keir Fraser
2009-09-30 11:27 ` Samuel Thibault
2009-09-30 13:56 ` Keir Fraser
2009-09-30 15:45 ` Christoph Egger [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=200909301745.24829.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=keir.fraser@eu.citrix.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 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.