[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160419113501.GA10638@cz.tnic>
Date: Tue, 19 Apr 2016 13:35:01 +0200
From: Borislav Petkov <bp@...en8.de>
To: Ingo Molnar <mingo@...nel.org>
Cc: peterz@...radead.org, dsafonov@...tuozzo.com, luto@...nel.org,
hpa@...or.com, dvlasenk@...hat.com, luto@...capital.net,
torvalds@...ux-foundation.org, brgerst@...il.com,
linux-kernel@...r.kernel.org, tglx@...utronix.de,
linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/asm] x86/entry: Rename is_{ia32,x32}_task() to
in_{ia32,x32}_syscall()
On Tue, Apr 19, 2016 at 01:15:30PM +0200, Ingo Molnar wrote:
> So I'd suggest the following renames to harmonize these concepts:
>
> - CONFIG_IA32_EMULATION => CONFIG_X86_32_ABI
> this lines up nicely with: CONFIG_X86_X32_ABI
Except that the only difference now is the "X" in the strings. So one
would need more coffee when staring at those. :)
>
> - is_ia32_syscall() -> is_x86_32_syscall()
> - is_x32_syscall() -> is_x86_x32_syscall()
>
> - is_compat_syscall() remains as-is.
>
> ... thoughts?
Still, getting those names streamlined and logical is a step in the
right direction IMO.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply. Srsly.
Powered by blists - more mailing lists