public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Ian Campbell <Ian.Campbell@xensource.com>
Cc: Andre Noll <maan@systemlinux.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	Andy Whitcroft <apw@shadowen.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 14:05:03 +0200	[thread overview]
Message-ID: <200609271405.03849.ak@suse.de> (raw)
In-Reply-To: <1159355329.28313.29.camel@localhost.localdomain>


> The xen-unstable tree has had the .bss movement patch in for a couple of
> weeks now with no reported bugs. We are frozen for the release 3.0.3 so
> at least in theory people should be testing it pretty hard ;-)

Ok maybe we should retry it. The BSS movement patch makes sense by
itself after all and in theory really shouldn't break anything.
I'll reenable it.

-Andi

  reply	other threads:[~2006-09-27 12:05 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
2006-09-27 11:08           ` Ian Campbell
2006-09-27 12:05             ` Andi Kleen [this message]
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=200609271405.03849.ak@suse.de \
    --to=ak@suse.de \
    --cc=Ian.Campbell@xensource.com \
    --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