mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: davej@redhat.com, akpm@osdl.org, ak@muc.de, jeff@garzik.org,
	torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86-64 build fix
Date: Thu, 22 Jun 2006 16:37:24 -0700	[thread overview]
Message-ID: <20060622163724.5b360e83.rdunlap@xenotime.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0606230124350.17704@scrub.home>

On Fri, 23 Jun 2006 01:28:01 +0200 (CEST) Roman Zippel wrote:

> Hi,
> 
> On Thu, 22 Jun 2006, Dave Jones wrote:
> 
> > On Thu, Jun 22, 2006 at 03:59:43PM -0700, 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.
> > 
> > Not guilty your honour.
> > See my mail..
> > Subject: Re: intelfb: enable on x86_64
> > 
> > It got busted due to INTEL_FB becoming available on x86-64, and it doing
> > select AGP which if INTEL_FB was =m turned CONFIG_AGP=y into CONFIG_AGP=m
> > for who-knows-why reason.  This busts the IOMMU code which expects the AGP
> > code to be =y or =n
> 
> The select overrides the default (it actually overrides pretty much 
> everything, that's why one should be careful with it).

Just checking:  so the "select AGP"
sets CONFIG_AGP to the same level or value (m or y) as the option
where it is being used?


---
~Randy

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22 20:59 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 [this message]
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

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=20060622163724.5b360e83.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®