From: "H. Peter Anvin" <hpa@zytor.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, mingo@redhat.com, sam@ravnborg.org,
tglx@linutronix.de, David.Woodhouse@intel.com,
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 09:27:18 -0700 [thread overview]
Message-ID: <4AA13FE6.20807@zytor.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0909041631210.14872@twosheds.infradead.org>
On 09/04/2009 08:33 AM, David Woodhouse wrote:
> On Fri, 4 Sep 2009, Ingo Molnar wrote:
>
>
>>> x86: Don't silently override CONFIG_64BIT in 'make oldconfig'
>>
>> -tip testing found that this commit broke the UML build:
>>
>> /home/mingo/tip/arch/um/Makefile:52:
>> /home/mingo/tip/arch/um/Makefile-x86: No such file or directory
>> make[1]: *** No rule to make target
>> `/home/mingo/tip/arch/um/Makefile-x86'. Stop.
>> make: *** [sub-make] Error 2
>
> Hm, doesn't that mean that UML has always been broken for ARCH=x86?
>
Quite possible. ARCH=x86 hasn't exactly been widely used.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-09-04 16:33 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 ` [tip:x86/kbuild] x86: Don't silently override CONFIG_64BIT in 'make oldconfig' Ingo Molnar
2009-09-04 15:33 ` David Woodhouse
2009-09-04 16:27 ` H. Peter Anvin [this message]
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
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=4AA13FE6.20807@zytor.com \
--to=hpa@zytor.com \
--cc=David.Woodhouse@intel.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=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 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.