From: Borislav Petkov <bp@alien8.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Andy Lutomirski <luto@amacapital.net>,
Denys Vlasenko <dvlasenk@redhat.com>,
Brian Gerst <brgerst@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC PATCH] Rename ia32entry.S to entry_64_compat_32.S
Date: Fri, 5 Jun 2015 15:37:14 +0200 [thread overview]
Message-ID: <20150605133714.GH3679@pd.tnic> (raw)
In-Reply-To: <1433509230-22238-1-git-send-email-mingo@kernel.org>
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.
--
next prev parent reply other threads:[~2015-06-05 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 13:00 [RFC PATCH] Rename ia32entry.S to entry_64_compat_32.S Ingo Molnar
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 ` Borislav Petkov [this message]
2015-06-05 21:09 ` [RFC PATCH] Rename ia32entry.S to entry_64_compat_32.S 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=20150605133714.GH3679@pd.tnic \
--to=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=mingo@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox