All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Andi Kleen <ak@muc.de>
Cc: Jeff Garzik <jeff@garzik.org>, Andrew Morton <akpm@osdl.org>,
	torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86-64 build fix
Date: Thu, 22 Jun 2006 20:23:49 -0400	[thread overview]
Message-ID: <20060623002348.GF5604@redhat.com> (raw)
In-Reply-To: <20060622233549.GA55538@muc.de>

On Fri, Jun 23, 2006 at 01:35:49AM +0200, Andi Kleen wrote:
 > On Thu, Jun 22, 2006 at 07:23:58PM -0400, Jeff Garzik wrote:
 > > Andrew Morton wrote:
 > > >I don't think Jeff has sent us an example .config, but I hit this a few
 > > >times too, before we fixed it.  I think this was all triggered by a Kconfig
 > > >change in the AGP tree, so you wouldn't have seen it, but -mm did.
 > > 
 > > 'make allmodconfig' on x86-64.  You can create this .config yourself :)
 > > 
 > > I think the tree suffers [sometimes due to me :(] when 'allyesconfig' 
 > > and 'allmodconfig' stop working.
 > 
 > Yes, but they work in 2.6.17 right? 

worked for me, it only broke as of .17-git2 or so.

 > And nothing should have changed since 2.6.17 so far.
 > But apparently something did. What was it?

(for the 3rd time today)  INTEL_FB now builds on x86-64,
and selects AGP, so if INTEL_FB=m, AGP becomes =m too,
which breaks the select AGP which GART_IOMMU wants.

		Dave

-- 
http://www.codemonkey.org.uk

      reply	other threads:[~2006-06-23  0:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22 20:59 [PATCH] x86-64 build fix Jeff Garzik
2006-06-22 21:24 ` Andrew Morton
2006-06-22 22:39   ` Andi Kleen
2006-06-22 22:59     ` Andrew Morton
2006-06-22 23:01       ` Dave Jones
2006-06-22 23:28         ` Roman Zippel
2006-06-22 23:37           ` Randy.Dunlap
2006-06-23  0:27             ` Roman Zippel
2006-06-22 23:23       ` Jeff Garzik
2006-06-22 23:35         ` Andi Kleen
2006-06-23  0:23           ` Dave Jones [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=20060623002348.GF5604@redhat.com \
    --to=davej@redhat.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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.