[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 6 Jun 2014 14:14:20 -0700
From: Andy Lutomirski <luto@...capital.net>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
"H. Peter Anvin" <hpa@...ux.intel.com>,
Cyrill Gorcunov <gorcunov@...nvz.org>,
Peter Anvin <hpa@...or.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Sasha Levin <sasha.levin@...cle.com>,
Stefani Seibold <stefani@...bold.net>,
Thomas Gleixner <tglx@...utronix.de>,
Pavel Emelyanov <xemul@...allels.com>
Subject: Re: [GIT PULL] x86/vdso changes for v3.16
On Fri, Jun 6, 2014 at 2:13 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> On Fri, Jun 6, 2014 at 2:09 PM, Andy Lutomirski <luto@...capital.net> wrote:
>>
>> The only real downside to that would be the chance of bitrot if that
>> code isn't getting used on native builds.
>
> Sure. Does anybody really care?
>
> You could obviously just open-code the things, but the fact is,
> "le64toh()" isn't exactly a standard function anyway, so now that I
> see it needed I go "yeah, that's clearly completely unacceptable".
>
> I'd much rather say "screw cross-compiling" (because let's face it,
> nobody sane cross-compiles x86 on anything else) than say "screw old
> machines".
Tell that to Stephen Rothwell, who apparently cross-compiles x86 on
ppc on a regular basis :)
I'll send a patch.
--Andy
--
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