From: Ian Campbell <Ian.Campbell@XenSource.com>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Andi Kleen <ak@suse.de>, Andre Noll <maan@systemlinux.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Martin Bligh <mbligh@google.com>, Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.18-mm1 compile failure on x86_64
Date: Wed, 27 Sep 2006 12:24:24 +0100 [thread overview]
Message-ID: <1159356267.28313.33.camel@localhost.localdomain> (raw)
In-Reply-To: <451A5AD3.6060403@shadowen.org>
On Wed, 2006-09-27 at 12:04 +0100, Andy Whitcroft wrote:
> In my testing, backing out the old patch and putting the one mentioned
> in the following message seems to work:
>
> http://lists.xensource.com/archives/html/xen-devel/2006-08/msg01416.html
FWIW that's the same as applying
http://marc.theaimsgroup.com/?l=linux-kernel&m=115567883710134&w=2 over
the original patch, which is the fix I was talking about in my previous
mail.
Ian.
next prev parent reply other threads:[~2006-09-27 11:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 22:39 2.6.18-mm1 compile failure on x86_64 Martin Bligh
2006-09-25 22:43 ` Jeff Garzik
2006-09-25 22:50 ` Martin Bligh
2006-09-26 6:41 ` Andi Kleen
2006-09-26 7:07 ` Andrew Morton
2006-09-26 7:09 ` Andi Kleen
2006-09-26 7:51 ` Andy Whitcroft
2006-09-26 8:29 ` Jeremy Fitzhardinge
2006-09-26 8:48 ` Ian Campbell
2006-09-27 9:17 ` Andy Whitcroft
2006-09-26 12:44 ` Andy Whitcroft
2006-09-27 1:35 ` Eric W. Biederman
2006-09-27 9:58 ` Andre Noll
2006-09-27 10:26 ` Andi Kleen
2006-09-27 11:04 ` Andy Whitcroft
2006-09-27 11:24 ` Ian Campbell [this message]
2006-09-27 11:08 ` Ian Campbell
2006-09-27 12:05 ` Andi Kleen
2006-09-27 14:11 ` Eric W. Biederman
2006-09-27 16:53 ` Andy Whitcroft
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=1159356267.28313.33.camel@localhost.localdomain \
--to=ian.campbell@xensource.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=ebiederm@xmission.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maan@systemlinux.org \
--cc=mbligh@google.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