Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752183AbbFENhU (ORCPT ); Fri, 5 Jun 2015 09:37:20 -0400 Received: from mail.skyhub.de ([78.46.96.112]:35747 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751389AbbFENhR (ORCPT ); Fri, 5 Jun 2015 09:37:17 -0400 Date: Fri, 5 Jun 2015 15:37:14 +0200 From: Borislav Petkov To: Ingo Molnar Cc: linux-kernel@vger.kernel.org, Andy Lutomirski , Denys Vlasenko , Brian Gerst , Peter Zijlstra , "H. Peter Anvin" , Linus Torvalds , Oleg Nesterov , Thomas Gleixner Subject: Re: [RFC PATCH] Rename ia32entry.S to entry_64_compat_32.S Message-ID: <20150605133714.GH3679@pd.tnic> References: <1433509230-22238-1-git-send-email-mingo@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1433509230-22238-1-git-send-email-mingo@kernel.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 934 Lines: 29 On Fri, Jun 05, 2015 at 03:00:29PM +0200, Ingo Molnar wrote: > I'm wondering what people think about this naming scheme: > > entry_32.S # 32-bit binaries on 32-bit kernels > entry_64.S # 64-bit binaries on 64-bit kernels > entry_64_compat_32.S # 32-bit binaries on 64-bit kernels > > Another option would be: > > arch/x86/entry/sys_32.S > arch/x86/entry/sys_64.S > arch/x86/entry/sys_64_compat.S I like this one better because entry_64_compat_32 kinda has both bitness in there and confuses me more. Just my 2 ยข. :) -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. -- -- 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/