[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071119160024.GA11309@alberich.amd.com>
Date: Mon, 19 Nov 2007 17:00:24 +0100
From: "Andreas Herrmann" <andreas.herrmann3@....com>
To: "Sam Ravnborg" <sam@...nborg.org>
cc: "Andreas Herrmann" <aherrman@...or.de>,
"Linus Torvalds" <torvalds@...ux-foundation.org>,
"Thomas Gleixner" <tglx@...utronix.de>,
"Ingo Molnar" <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>,
"Roman Zippel" <zippel@...ux-m68k.org>,
"LKML" <linux-kernel@...r.kernel.org>,
"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: [PATCH] x86: fix UTS_MACHINE to be i386 for 32-bit build
and x86_64 for 64-bit build
On Mon, Nov 19, 2007 at 11:41:29AM +0100, Sam Ravnborg wrote:
> On Mon, Nov 19, 2007 at 10:34:37AM +0100, Andreas Herrmann wrote:
> > On Sat, Nov 17, 2007 at 03:37:31PM +0100, Sam Ravnborg wrote:
> > >
> > > Note: This patch does not fix the uname -m issue - to do so
> > > Andreas' patch is needed.
> > >
> > > Sam
> >
> > Linus,
> >
> > The issue Sam refers to is that UTS_MACHINE is set to "x86" instead of
> > "i386" or "x86_64" when building with ARCH=x86. Thus the new kernel
> > when booted will give either "x86" on x86_64 and many i386 systems or
> > even "x66" on other i386 systems for 'uname -m'.
> >
> > Many tools rely on the usual values of "x86_64", "i366" and "i686"
> > here. So we shouldn't change this.
>
> Andreas - I will suggest you to submit a new patch with
> a better changelog where you jsut describe what you fix.
> The above explanations looks a bit weird if read stand alone.
Ok, I'll resend the patch with an updated changelog asap.
> You can always add additional comments after the line containing:
> ---
>
> In this way it is not included in the changelog but Linus can read it.
>
> Anyway - your patch has my ack.
Thanks,
Andreas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists