[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150324193457.GB23521@gmail.com>
Date: Tue, 24 Mar 2015 20:34:57 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Denys Vlasenko <dvlasenk@...hat.com>,
Andy Lutomirski <luto@...capital.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Steven Rostedt <rostedt@...dmis.org>,
"H. Peter Anvin" <hpa@...or.com>, Oleg Nesterov <oleg@...hat.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Alexei Starovoitov <ast@...mgrid.com>,
Will Drewry <wad@...omium.org>,
Kees Cook <keescook@...omium.org>, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/asm/entry/64: Rename THREAD_INFO() to
ASM_ASM_THREAD_INFO_MEMOP()
* Borislav Petkov <bp@...en8.de> wrote:
> On Tue, Mar 24, 2015 at 07:44:42PM +0100, Ingo Molnar wrote:
> > From 234ed7356ecfa60f4e209d513d89fa9de41aa4c5 Mon Sep 17 00:00:00 2001
> > From: Ingo Molnar <mingo@...nel.org>
> > Date: Tue, 24 Mar 2015 19:29:16 +0100
> > Subject: [PATCH] x86/asm/entry/64: Rename THREAD_INFO() to ASM_ASM_THREAD_INFO_MEMOP()
> >
> > The THREAD_INFO() macro has a somewhat confusingly generic name, defined in
> > a generic .h C header file. It also does not make it clear that it constructs
> > a memory operand for use in assembly code.
> >
> > Rename it to ASM_THREAD_INFO_MEMOP() to make it all glaringly obvious on
> > first glance.
>
> Why the MEMOP?
>
> ASM_THREAD_INFO() looks pretty enough to me. :)
Ok.
Thanks,
Ingo
--
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/
Powered by blists - more mailing lists