From: Keir Fraser <keir.xen@gmail.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Juergen Gross <juergen.gross@ts.fujitsu.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Kay, Allen M" <allen.m.kay@intel.com>
Subject: Re: build failure caused by $(XEN_ROOT)/.config
Date: Thu, 06 Oct 2011 19:27:21 +0100 [thread overview]
Message-ID: <CAB3B199.224C2%keir.xen@gmail.com> (raw)
In-Reply-To: <20109.59774.489643.241603@mariner.uk.xensource.com>
On 06/10/2011 18:46, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:
> Juergen Gross writes ("Re: [Xen-devel] build failure caused by
> $(XEN_ROOT)/.conf> His build path suggests he is using xen-4.1-testing.
> cs23049 was applied directly
>> after branching xen 4.1.
>> In the current staging tree my patch fixes a similar problem in a different
>> Makefile.
>>
>> Allen, which version are you really using?
>
> To summarise, it sounds like we need to backport 23049 to 4.1 but also
> to apply Juergen's patch to libfsimage ?
Sounds about right. If you want to do an equivalent patch to 23049 in 4.1
feel free to go ahead. I'll hold back -rc3 in that case.
-- Keir
> Ian.
next prev parent reply other threads:[~2011-10-06 18:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 21:44 build failure caused by $(XEN_ROOT)/.config Kay, Allen M
2011-10-05 4:45 ` Juergen Gross
2011-10-05 16:24 ` Kay, Allen M
2011-10-05 16:42 ` Keir Fraser
2011-10-05 16:43 ` Keir Fraser
2011-10-05 16:47 ` Brendan Cully
2011-10-05 16:51 ` Keir Fraser
2011-10-05 16:56 ` Ian Campbell
2011-10-06 4:40 ` Juergen Gross
2011-10-06 8:00 ` Keir Fraser
2011-10-06 8:11 ` Juergen Gross
2011-10-06 17:46 ` Ian Jackson
2011-10-06 18:27 ` Keir Fraser [this message]
2011-10-06 18:18 ` Kay, Allen M
2011-10-06 18:23 ` Ian Jackson
2011-10-06 18:27 ` Kay, Allen M
2011-10-06 18:33 ` Keir Fraser
2011-10-06 18:39 ` Kay, Allen M
2011-10-06 18:50 ` Ian Jackson
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=CAB3B199.224C2%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=allen.m.kay@intel.com \
--cc=juergen.gross@ts.fujitsu.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.