From: Adrian Bunk <bunk@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Sam Ravnborg <sam@ravnborg.org>,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [2.6.24 patch] x86: allow 64bit setting in Kconfig
Date: Fri, 18 Jan 2008 19:26:30 +0200 [thread overview]
Message-ID: <20080118172630.GD28233@does.not.exist> (raw)
In-Reply-To: <20080118170037.GA23297@elte.hu>
On Fri, Jan 18, 2008 at 06:00:37PM +0100, Ingo Molnar wrote:
>
> * Ingo Molnar <mingo@elte.hu> wrote:
>
> >
> > * Adrian Bunk <bunk@kernel.org> wrote:
> >
> > > # Select 32 or 64 bit
> > > config 64BIT
> > > - bool "64-bit kernel" if ARCH = "x86"
> > > + bool "64-bit kernel"
> > > default ARCH = "x86_64"
> > > help
> > > Say yes to build a 64-bit kernel - formerly known as x86_64
> >
> > thx, i've added this to x86.git.
>
> this broke "make ARCH=i386 randconfig" from working when there's a
> 64-bit .config present. (it will not properly generate a 32-bit config,
> but still a 64-bit config)
Does it always generate a 64bit .config or randomly a 32bit or 64bit
.config?
As far as I see it's the latter.
If the unified x86 architecture should be presented as one
architecture in kconfig that's expected - and it might even reduce the
amount of 32bit compile errors that recently occured in the git-x86
tree...
> Ingo
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-01-18 17:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 21:43 [2.6.24 patch] x86: allow 64bit setting in Kconfig Adrian Bunk
2008-01-18 10:44 ` Ingo Molnar
2008-01-18 10:50 ` Harvey Harrison
2008-01-18 11:37 ` Sam Ravnborg
2008-01-18 12:02 ` Ingo Molnar
2008-01-18 12:09 ` Adrian Bunk
2008-01-18 11:48 ` Ingo Molnar
2008-01-18 17:00 ` Ingo Molnar
2008-01-18 17:26 ` Adrian Bunk [this message]
2008-01-18 21:06 ` Ingo Molnar
2008-01-18 21:23 ` Adrian Bunk
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=20080118172630.GD28233@does.not.exist \
--to=bunk@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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