From: "H. Peter Anvin" <hpa@zytor.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, mingo@redhat.com, sam@ravnborg.org,
tglx@linutronix.de, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/kbuild] x86: Don't silently override CONFIG_64BIT in 'make oldconfig'
Date: Fri, 04 Sep 2009 15:54:38 -0700 [thread overview]
Message-ID: <4AA19AAE.9050909@zytor.com> (raw)
In-Reply-To: <1252100456.4483.544.camel@macbook.infradead.org>
On 09/04/2009 02:40 PM, David Woodhouse wrote:
> On Fri, 2009-09-04 at 09:38 -0700, Randy Dunlap wrote:
>>
>> what does ARCH=x86 mean?
>
> A bit like ARCH=powerpc. It's the new combined architecture where 64-bit
> vs. 32-bit is just a config choice. ARCH=i386 and ARCH=x86_64 are just
> historical baggage, and should be dropped like ARCH=ppc and ARCH=ppc64
> were.
>
>From a cursory look it looks like ARCH=powerpc won't work for UM, either.
-hpa
next prev parent reply other threads:[~2009-09-04 22:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-5a8a2d13b1526e306ff2a9fe12dc9d5878d355f9@git.kernel.org>
2009-09-04 14:48 ` Ingo Molnar
2009-09-04 15:33 ` David Woodhouse
2009-09-04 16:27 ` H. Peter Anvin
2009-09-04 16:38 ` Randy Dunlap
2009-09-04 16:53 ` H. Peter Anvin
2009-09-04 21:40 ` David Woodhouse
2009-09-04 22:54 ` H. Peter Anvin [this message]
2009-09-04 18:31 ` Ingo Molnar
2009-09-04 18:57 ` H. Peter Anvin
2009-09-04 19:04 ` H. Peter Anvin
2009-09-11 21:16 ` Jeff Dike
2009-09-14 23:29 ` H. Peter Anvin
2009-09-15 3:33 ` Jeff Dike
2009-09-25 9:03 ` H. Peter Anvin
2009-09-28 4:31 ` Sam Ravnborg
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=4AA19AAE.9050909@zytor.com \
--to=hpa@zytor.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=randy.dunlap@oracle.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
Powered by JetHome