Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752506AbbFEVLC (ORCPT ); Fri, 5 Jun 2015 17:11:02 -0400 Received: from terminus.zytor.com ([198.137.202.10]:34712 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751429AbbFEVK7 (ORCPT ); Fri, 5 Jun 2015 17:10:59 -0400 User-Agent: K-9 Mail for Android In-Reply-To: <20150605133714.GH3679@pd.tnic> References: <1433509230-22238-1-git-send-email-mingo@kernel.org> <20150605133714.GH3679@pd.tnic> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: [RFC PATCH] Rename ia32entry.S to entry_64_compat_32.S From: "H. Peter Anvin" Date: Fri, 05 Jun 2015 14:09:11 -0700 To: Borislav Petkov , Ingo Molnar CC: linux-kernel@vger.kernel.org, Andy Lutomirski , Denys Vlasenko , Brian Gerst , Peter Zijlstra , Linus Torvalds , Oleg Nesterov , Thomas Gleixner Message-ID: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1181 Lines: 34 Call it sys if it is now only the system call entry points. Agreed with _64_compat too. Breaking up these snarls of spaghetti assembly will be a blessing. On June 5, 2015 6:37:14 AM PDT, Borislav Petkov wrote: >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 ยข. :) -- Sent from my mobile phone. Please pardon brevity and lack of formatting. -- 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/