From: David Woodhouse <dwmw2@infradead.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jeff Dike <jdike@addtoit.com>, Sam Ravnborg <sam@ravnborg.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ARCH=x86 patch
Date: Fri, 25 Sep 2009 02:50:46 -0700 [thread overview]
Message-ID: <1253872246.4310.1448.camel@macbook.infradead.org> (raw)
In-Reply-To: <4ABC8F50.2030006@zytor.com>
On Fri, 2009-09-25 at 02:37 -0700, H. Peter Anvin wrote:
> I am confused, because I could have sworn I had tested this combination
> already, but having applied Jeff's UM fix and then David's ARCH=x86
> patch on top of that, I now find that all the 32-bit builds crap out
> when building on a 64-bit platform, due to asm-offsets.c being compiled
> with -m64 rather than -m32.
Argh.
All this nonsense simply because Ingo objected to my previous patch...
purely on the basis that it made 'make randconfig' actually random.
--
dwmw2
prev parent reply other threads:[~2009-09-25 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 9:37 H. Peter Anvin
2009-09-25 9:50 ` David Woodhouse [this message]
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=1253872246.4310.1448.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=hpa@zytor.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®