From: Arjan van de Ven <arjan@infradead.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] replace "make ARCH=i386/x86_64 with make ARCH=x86"
Date: Sat, 3 Nov 2007 16:52:47 -0700 [thread overview]
Message-ID: <20071103165247.3663f518@laptopd505.fenrus.org> (raw)
In-Reply-To: <20071103234826.GA26654@uranus.ravnborg.org>
On Sun, 4 Nov 2007 00:48:26 +0100
Sam Ravnborg <sam@ravnborg.org> wrote:
> This patchset unify the i386 and x86_64 Kconfig
> files for x86.
> In addition it replaces the use of ARCH=i386 and
> ARCH=x86_64 with the more intuitive ARCH=x86.
>
> The primary purpose of this patch serie is to
> enable make ARCH=x86 and let the config decide
> if we are building for 32 or 64 bit.
>
> But we will break quite a high number of
> scripts with this change.
> What is the desired behaviour when specifying:
> make ARCH=i386
> and
> make ARCH=x86_64
I would say.. just print a very very nasty warning, wait 20 seconds,
and then pretend it was passed as x86
and then remove in the next release (assuming the code isn't too ugly)
other than that.. just break it now in 2.6.24; people at least remember
.24 as the release that unified, so they expect changes there... they
won't expect them for .25 or later
next prev parent reply other threads:[~2007-11-03 23:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 23:48 Sam Ravnborg
2007-11-03 23:52 ` Arjan van de Ven [this message]
2007-11-04 1:17 ` Adrian Bunk
2007-11-04 2:02 ` Jeff Garzik
2007-11-04 2:48 ` Adrian Bunk
2007-11-04 6:20 ` Jeremy Fitzhardinge
2007-11-05 10:41 ` Christoph Hellwig
2007-11-05 17:17 ` Sam Ravnborg
2007-11-05 21:36 ` Roland Dreier
2007-11-05 21:49 ` Sam Ravnborg
2007-11-05 23:46 ` H. Peter Anvin
2007-11-06 0:40 ` Guillaume Chazarain
2007-11-06 0:47 ` H. Peter Anvin
2007-11-06 1:29 ` Adrian Bunk
2007-11-06 1:33 ` H. Peter Anvin
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=20071103165247.3663f518@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®