Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752240AbaFFVNH (ORCPT ); Fri, 6 Jun 2014 17:13:07 -0400 Received: from mail-vc0-f179.google.com ([209.85.220.179]:35596 "EHLO mail-vc0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751901AbaFFVNG (ORCPT ); Fri, 6 Jun 2014 17:13:06 -0400 MIME-Version: 1.0 In-Reply-To: References: <201406042235.s54MZgwP020553@terminus.zytor.com> <20140606140017.afb7f91142f66cb3dd13c186@linux-foundation.org> Date: Fri, 6 Jun 2014 14:13:04 -0700 X-Google-Sender-Auth: C7AIHcdlH9gq1mN45uQXLO84Mgk Message-ID: Subject: Re: [GIT PULL] x86/vdso changes for v3.16 From: Linus Torvalds To: Andy Lutomirski Cc: Andrew Morton , "H. Peter Anvin" , Cyrill Gorcunov , Peter Anvin , Linux Kernel Mailing List , Ingo Molnar , Sasha Levin , Stefani Seibold , Thomas Gleixner , Pavel Emelyanov Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 6, 2014 at 2:09 PM, Andy Lutomirski 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". Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/