All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Andy Lutomirski <luto@amacapital.net>,
	Denys Vlasenko <dvlasenk@redhat.com>,
	Brian Gerst <brgerst@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Oleg Nesterov <oleg@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: [RFC PATCH] Rename ia32entry.S to entry_64_compat_32.S
Date: Fri,  5 Jun 2015 15:00:29 +0200	[thread overview]
Message-ID: <1433509230-22238-1-git-send-email-mingo@kernel.org> (raw)

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


             reply	other threads:[~2015-06-05 13:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05 13:00 Ingo Molnar [this message]
2015-06-05 13:00 ` [PATCH] x86/asm/entry/64/compat: Rename ia32entry.S -> entry_64_compat_32.S Ingo Molnar
2015-06-05 14:02   ` Brian Gerst
2015-06-05 13:37 ` [RFC PATCH] Rename ia32entry.S to entry_64_compat_32.S Borislav Petkov
2015-06-05 21:09   ` H. Peter Anvin
2015-06-05 21:37     ` Andy Lutomirski
2015-06-07 12:58       ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1433509230-22238-1-git-send-email-mingo@kernel.org \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=dvlasenk@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.