linux-kernel - [RFC PATCH] Rename ia32entry.S to entry_64_compat

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1433509230-22238-1-git-send-email-mingo@kernel.org>
Date:	Fri,  5 Jun 2015 15:00:29 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	linux-kernel@...r.kernel.org
Cc:	Andy Lutomirski <luto@...capital.net>,
	Denys Vlasenko <dvlasenk@...hat.com>,
	Brian Gerst <brgerst@...il.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Borislav Petkov <bp@...en8.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Oleg Nesterov <oleg@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: [RFC PATCH] Rename ia32entry.S to entry_64_compat_32.S

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

?

Thanks,

    Ingo
===

Ingo Molnar (1):
  x86/asm/entry/64/compat: Rename ia32entry.S -> entry_64_compat_32.S

 arch/x86/entry/Makefile                              | 2 +-
 arch/x86/entry/entry_64.S                            | 2 +-
 arch/x86/entry/{ia32entry.S => entry_64_compat_32.S} | 0
 3 files changed, 2 insertions(+), 2 deletions(-)
 rename arch/x86/entry/{ia32entry.S => entry_64_compat_32.S} (100%)

-- 
2.1.4

--
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/