From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@elte.hu>, Jeff Dike <jdike@addtoit.com>,
Sam Ravnborg <sam@ravnborg.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org, mingo@redhat.com,
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 12:04:32 -0700 [thread overview]
Message-ID: <4AA164C0.9080003@zytor.com> (raw)
In-Reply-To: <4AA16336.3050606@zytor.com>
On 09/04/2009 11:57 AM, H. Peter Anvin wrote:
>
> Anyway... it sounds like we need to drop this commit for now and
> re-merge it when there is a fix for UM.
>
> Jeff, Sam, I would appreciate your suggestions as how best to fix this
> kind of stuff...
>
On that note, this issue isn't just limited to UM. klibc has to deal
with this issue too: a single kernel architecture may correspond to more
than one user-space architecture, and as far as userspace is concerned,
they are completely different.
-hpa
next prev parent reply other threads:[~2009-09-04 19:08 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
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 [this message]
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=4AA164C0.9080003@zytor.com \
--to=hpa@zytor.com \
--cc=David.Woodhouse@intel.com \
--cc=dwmw2@infradead.org \
--cc=jdike@addtoit.com \
--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.