From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH/RFC] x86: unify Kconfig files
Date: Wed, 31 Oct 2007 21:08:03 -0700 [thread overview]
Message-ID: <47295123.9010603@goop.org> (raw)
In-Reply-To: <20071031215501.GA28556@uranus.ravnborg.org>
Sam Ravnborg wrote:
> It has been requested that we should let x86 behave like
> other architectures so we at config time decide for 32 or 64 bit.
> The challenge here is to mere the Kconfig files and I have done
> an attempt to do so.
>
> +source "mm/Kconfig"
>
> -config X86_VISWS_APIC
> +config HIGHPTE
> + bool "Allocate 3rd-level pagetables from highmem"
> + depends on X86_32 && HIGHMEM4G || HIGHMEM64G
>
Some parens: X86_32 && (HIGHMEM4G || HIGHMEM64G)?
J
next prev parent reply other threads:[~2007-11-01 4:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 21:55 [PATCH/RFC] x86: unify Kconfig files Sam Ravnborg
2007-11-01 4:08 ` Jeremy Fitzhardinge [this message]
2007-11-01 5:25 ` Sam Ravnborg
2007-11-01 21:14 ` Sam Ravnborg
2007-11-01 21:21 ` H. Peter Anvin
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=47295123.9010603@goop.org \
--to=jeremy@goop.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
/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